Dev #866
Merged
Dev #866
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge dev to main
Clusters marked as deleted are scheduled for removal once their finalizer is removed. Therefore, initiating cleanup while a cluster is in this state is redundant. Prior to this change, Sveltos would trigger cleanup for a cluster instance even if it was marked as deleted. However, if Sveltos invoked the Helm SDK as part of the cleanup and the Helm uninstall client encountered an unreachable cluster api-server, the Helm SDK would become stuck. To prevent this issue and avoid unnecessary feature cleanup for clusters marked for deletion, this PR has been implemented.
(bug) when cluster is marked as deleted avoid triggering cleanup
…lidation Skip schema validation
Set GOMAXPROCS
…nup" Sveltos deploys resources in the management cluster when the `deploymenType` is set to `Local`. Even if a cluster is marked as deleted, Sveltos will still need to remove all resources deployed in the management cluster for that cluster. So this PR lets Sveltos undeploy even for clusters marked as deleted. If the managed cluster API server is unreachable after the Helm SDK uninstall is triggered, the Helm SDK will get stuck. Helm charts are only deployed in the matching cluster, so Sveltos will skip calling Helm uninstall for any deleted cluster. This reverts commit ce9e7f6.
Revert "(bug) when cluster is marked as deleted avoid triggering clea…
Prepare for release v0.39.0
bump clusterapi to v1.8.4
(chore): bump golangci-lint to v1.61.0
(chore) bump helm
In large cluster, number of Secrets and ConfigMaps might be high. Do not cache those. In order to avoid fetching the Secret with cluster Kubeconfig, create a in memory cluster cache with restConfig. This feature is currently disabled. To enable set `disable-secret-caching=true`
Cluster's rest config cache
(chore) prepare for release v0.40.0
Signed-off-by: Oliver Bähler <oliverbaehler@hotmail.com>
feat(deps): add renovate config
When cluster is still present but marked as deleted, Sveltos can avoid removing resources (helm charts and/or kubernetes resources) from such a cluster. Anything else created in the management cluster for such managed cluster still needs to be removed.
(bug) better handle deleted cluster
It was incorrectly pointing to a libsveltos fork
(chore) fix go mod
DisableHooks is already exposed at HelmOptions level and applies to install/upgrade/uninstall. Sometimes it is convenient to disable hooks only for install or upgrade or uninstall. This PR exposes DisableHooks at: - HelmInstallOptions - HelmUpgradeOptions - HelmInstallOptions If set to true in one of the above, overrides the settings at HelmOptions level.
(feat) Expose DisableHooks for install/upgrade/uninstall
…functions (feat) add more template functions
…inx-stable-nginx-ingress-1.x chore(deps): update helm release nginx-stable/nginx-ingress to v1.4.2
…afana-grafana-8.x chore(deps): update helm release grafana/grafana to v8.6.2
…tio-istiod-1.x chore(deps): update helm release istio/istiod to v1.24.1
…tio-gateway-1.x chore(deps): update helm release istio/gateway to v1.24.1
…tio-base-1.x chore(deps): update helm release istio/base to v1.24.1
- getResource clears managedFields, resourceVersion and UID - removeField return object after modification
…functions (chore) fix getResource and removeField
…afana-grafana-8.x chore(deps): update helm release grafana/grafana to v8.6.3
…afana-grafana-8.x chore(deps): update helm release grafana/grafana to v8.6.3
…ometheus-community-prometheus-26.x chore(deps): update helm release prometheus-community/prometheus to v26
When in DryRun mode, Sveltos creates a ClusterReport containing the
list of changes compared to current configuration.
For raw Kubernetes resources this includes listing:
1. resources that would be created
2. resources that would be deleted
3. resources that would be updated
Sveltos now provides a more granular view of proposed changes during Dry Run mode
for updates. A detailed diff highlighting exact changes, such as added, modified,
or removed fields.
Example:
```yaml
resourceReports:
- action: Update
message: |
--- ClusterPolicy disallow-latest-tag
+++ ClusterPolicy disallow-latest-tag
@@ -49,7 +49,7 @@
name: validate-image-tag
skipBackgroundRequests: true
validate:
- message: Using a mutable image tag e.g. 'latest' is not allowed.
+ message: Using a mutable image tag e.g. 'latest' is not allowed in produdction clusters.
pattern:
spec:
```
…functions (feat): track full diff for resources
DryRun ClusterSummaries are periodically updated to reflect changes in the cluster. This PR ensures the Status is always set to Provisioning to avoid unnecessary reconciliations.
…iliations (perf) ClusterSummary in DryRun mode
…rifts Feature track drifts -- fixed clustername
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.