- current implementation:
listClusters(projectID: String!, clusterType: String): [Cluster!]! - updated Implementation:
listInfras(projectID: ID!, request: ListInfraRequest): ListInfraResponse!
Updated query:
Nageshbansal Nageshbansal
Nageshbansal
/ Litmusctl Upgrade.md
Last active
July 6, 2023 11:06
Nageshbansal
/ Upgarding Operator-SDK and Prometheus in LitmusChaos.md
Last active
May 25, 2023 06:08
As mentioned in the Operator-sdk If we decide to upgrade the Operator-sdk version, we have to keep in mind that post-1.0.0 minor releases (1.y) are designed to be backwards compatible and only introduce new functionalities. This means that we only need to regenerate the scaffolding for our operator using a newer version of Operator-SDK if we want to utilize the newly added features. If we prefer not to utilize these new features, the only necessary step is to update the operator image dependency (for Helm or Ansible operators) and rebuild the operator image.
Now here is the table which shows the changes required to upgrade the operator-sdk version. A dissucion can be done on the basis of requirements and features needed to from operator-sdk and then using following table mitigation can be taken care.
Nageshbansal
/ Self-observability of Query Subsystem in Skywalking-BanyanDB.md
Last active
May 24, 2023 14:32
Self-observability of Query Subsystem in Skywalking-BanyanDB
BanyanDB is a distributed database management system that offers a highly scalable and fault-tolerant solution for storing and processing large-scale data. To evaluate and improve the performance of BanyanDB's query subsystem, it is necessary to implement several features, such as self-observability and query plan visualization. I will implement the following tasks over the google summer of Code period: Implement EXPLAIN for both measure query and stream query to evaluate the query subsystem performance with real traffic and load. Add self-observability by implementing tracing and metrics to understand better how the internal physical plans work and identify any bottlenecks impacting query performance. Add support for EXPLAIN in the client SDK & CLI to make it easier for developers to use this feature and to enable them to optimize their queries. Add query plan visualization to the UI to make it easier for users to understand the execution plan of their queries and to identify any areas for optimi
