Repository navigation
Implement Argo Rollouts, NetworkPolicy, and PDB support - #7
Merged
Merged
Conversation
This file contains hidden or 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
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.
Enhancements and new features to the
baseHelm chart, focusing on improved support for Argo Rollouts, as well as adding first-class support for KubernetesNetworkPolicyandPodDisruptionBudgetresources. It also refactors service template rendering and updates documentation to reflect these changes. The chart version is bumped to0.3.0to indicate these breaking and featureful changes.The most important changes are:
Argo Rollouts Support and Service Handling
workload: rollout(Argo Rollouts), including a dedicatedrollout.yamlmanifest, special handling for rollout services, and automated merging of service references into rollout strategies for both canary and blue-green deployments. Additionally, thehttproute.yamltemplate now supports canary backend weights and a dedicated rollout service.NetworkPolicy and PodDisruptionBudget Resources
NetworkPolicyresource when enabled, with configurable selectors, policy types, ingress, and egress rules.PodDisruptionBudgetresource with validation for mutually exclusiveminAvailableandmaxUnavailablefields, as well as support forunhealthyPodEvictionPolicy.Template and Values Refactoring
_service.tpl) and updatedservice.yamland newservice-rollout.yamlto use this template, improving maintainability and consistency.updateStrategyin favor of a singlestrategyfield for all workload types, including rollouts.Documentation and Versioning
README.md) to reflect new features, parameter changes, and improved descriptions for rollout, network policy, and pod disruption budget support.Other Enhancements
hpa.yaml) to support referencingRolloutresources and to usewithfor resource utilization metrics, increasing flexibility.