Parham Doustdar
Parham Doustdar
We currently don't expose any metrics from Janitor controller, which makes us blind to how the garbage collection is going across different clusters. Now that Janitor controller is working across...
Right now, there is no way of refreshing the secret for the webhook without downtime. This command would generate a new secret and replace it with the current secret. This...
To improve user experience and prevent user errors, our validating webhook should do the following things. - For updates, it should make sure that the field which is modified is...
Steps to reproduce: 1. Modify the `apiMaster` field of a Cluster object so that Shipper will lose connection 2. Observe that the Cluster now has a field called `inservice` set...
When creating the conditions of the Release, we need to look at all the conditions of target objects, not just `ready`.
Right now, when `repo.FetchChartVersions` is called, it waits for 2 seconds as a timeout. This caused an incident when we tried to take down one of the chart repositories that...
Right now, we use the same instrumented client for all chart repositories. This is great because we expose some metrics about our requests to the chart repos, but it's not...
The user doesn't specify clusters by name. It's Shipper which decides the clusters that a Release should end up on. So, when we are processing an item and a Cluster...
When Shipper can't connect to an app cluster, the `strategy` field of the release doesn't get updated at all. To reproduce, create a release, wait for it to reach step...
Currently, when shipperctl is trying to set up the application cluster, it uses the service account that was created when "joining" the two clusters together. However, this adds an unnecessary...