Deployments become harder when one release changes both the machinery governing a Kubernetes platform and the workloads that depend on it. A new CustomResourceDefinition, admission webhook, controller, or routing API can change what the cluster accepts and how it behaves; a new application image can simultaneously depend on those changes. Argo CD and Argo Rollouts solve different parts of this problem.
Discovery
Learnings
- auto_storiesStories
- categoryAreas
- helpFAQ
- forumConversations
- descriptionPapers
- mailNewsletters
- video_libraryVideos
- timelineTimeline
Guidance
- codeTechnology of APIs
- business_centerBusiness of APIs
- campaignEvangelism of APIs
- gavelGovernance of APIs
- historyHistory of APIs
- account_balancePolitics of APIs
Toolbox
- domainProviders
- apiAPIs
- cloudSolutions
- buildTools
- verifiedStandards
- gavelRegulations
- horizontal_ruleHeaders
- layersOverlays
- extensionExtensions
- schemaSchema
- policyPolicies
- ruleRules