This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
feat!: add support to StatefulSet #59
Merged
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
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
leoporoli
approved these changes
Oct 3, 2024
leoporoli
reviewed
Oct 3, 2024
tedim52
reviewed
Oct 3, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds support to
apps/StatefulSetresources in k8s. In order to do it, it creates the concept of workloads. A service specify the workload which can be either anapps/Deploymentorapps/StatefulSet. As a consequence, it also results in breaking change in the plugin API. Instead of passing and returning theapps/DeploymentSpec, it will use thecore/PodSpecbecause it's a common data structure across the workloads.