-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm chart support #2641
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days |
Other advantages of using Helm charts:
|
Additional advantage:
|
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
And use the Helm templates (instead of Kustomize) to generate the standard Antrea YAML manifests (which are checked-in and uploaded as release assets). Standard manifests are generated based on Helm values files located under build/yamls/chart-values/, using a new script (./hack/generate-standard-manifests.sh). It is much faster than the old version. While I believe that using Helm directly and specifying YAML values whenever a new manifest needs to be generated would be better, the ./hack/generate-manifest.sh script is kept as-is, but it now uses Helm instead of Kustomize. Documentation for the Helm chart is autogenerated using helm-docs. In a future PR, we will look into the release process for the Helm chart. After that, Helm charts could be added for Antrea components (Flow Aggregator, Flow visibility). For #2641 Signed-off-by: Antonin Bas <[email protected]>
This issue is not resolved yet, there are still several changes required in order for the Helm chart to be usable by Antrea users. |
For each Antrea release, we generate the correct Helm chart archive and upload it as a release asset. The appropriate index.yaml file (Helm repo index) will be updated appropriately (in the antrea-io/website repository) and will be accessible through charts.antrea.io and / or antrea.io/charts. For antrea-io#2641 We are also moving all CRD resources from the generic templates/ directory to the special crds/ directory, in the Chart definition. This will cause Helm to treat CRDs as special resources, and in particular they will never be upgraded / deleted automatically by Helm. In particular, for upgrade, users will need to apply a separate YAML (which is being added to release assets) including all the CRD resource definitions. This represents an extra step, but ensures that users are aware that CRDs are being upgraded which may require some actions from them (e.g., migrate to a new version) and needs to be done with caution. Fixes antrea-io#3665 Signed-off-by: Antonin Bas <[email protected]>
For each Antrea release, we generate the correct Helm chart archive and upload it as a release asset. The appropriate index.yaml file (Helm repo index) will be updated appropriately (in the antrea-io/website repository) and will be accessible through charts.antrea.io and / or antrea.io/charts. For antrea-io#2641 We are also moving all CRD resources from the generic templates/ directory to the special crds/ directory, in the Chart definition. This will cause Helm to treat CRDs as special resources, and in particular they will never be upgraded / deleted automatically by Helm. In particular, for upgrade, users will need to apply a separate YAML (which is being added to release assets) including all the CRD resource definitions. This represents an extra step, but ensures that users are aware that CRDs are being upgraded which may require some actions from them (e.g., migrate to a new version) and needs to be done with caution. Fixes antrea-io#3665 Signed-off-by: Antonin Bas <[email protected]>
* Release Antrea Helm chart archive for each Antrea release For each Antrea release, we generate the correct Helm chart archive and upload it as a release asset. The appropriate index.yaml file (Helm repo index) will be updated appropriately (in the antrea-io/website repository) and will be accessible through charts.antrea.io and / or antrea.io/charts. For #2641 We are also moving all CRD resources from the generic templates/ directory to the special crds/ directory, in the Chart definition. This will cause Helm to treat CRDs as special resources, and in particular they will never be upgraded / deleted automatically by Helm. In particular, for upgrade, users will need to apply a separate YAML (which is being added to release assets) including all the CRD resource definitions. This represents an extra step, but ensures that users are aware that CRDs are being upgraded which may require some actions from them (e.g., migrate to a new version) and needs to be done with caution. Fixes #3665 Signed-off-by: Antonin Bas <[email protected]> * Address review comments Signed-off-by: Antonin Bas <[email protected]> * Fix build/charts/antrea/README.md Signed-off-by: Antonin Bas <[email protected]>
* repo URL is https://antrea.io/charts or https://charts.antrea.io * index is updated for every Antrea release starting with v1.8 For antrea-io/antrea#2641 Signed-off-by: Antonin Bas <[email protected]>
* repo URL is https://antrea.io/charts or https://charts.antrea.io * index is updated for every Antrea release starting with v1.8 For antrea-io/antrea#2641 Signed-off-by: Antonin Bas <[email protected]>
* repo URL is https://antrea.io/charts or https://charts.antrea.io * index is updated for every Antrea release starting with v1.8 For antrea-io/antrea#2641 Signed-off-by: Antonin Bas <[email protected]>
* repo URL is https://antrea.io/charts or https://charts.antrea.io * index is updated for every Antrea release starting with v1.8 For antrea-io/antrea#2641 Signed-off-by: Antonin Bas <[email protected]>
Antrea Helm chart repo is available at $ helm repo add antrea https://charts.antrea.io/
$ helm search repo --devel --regexp antrea
NAME CHART VERSION APP VERSION DESCRIPTION
antrea/antrea 1.8.0-alpha.2 1.8.0-alpha.2 Kubernetes networking based on Open vSwitch
antrea/flow-aggregator 1.8.0-alpha.2 1.8.0-alpha.2 Antrea Flow Aggregator
antrea/theia 0.2.0-alpha.0 0.2.0-alpha.0 Antrea Network Flow Visibility Helm installation method will be supported starting with Antrea v1.8.0. At this stage, the only thing left is to update the documentation with this new supported installation method. |
Fixes antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
Fixes antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
Fixes antrea-io#2641 Signed-off-by: Antonin Bas <[email protected]>
Fixes #2641 Signed-off-by: Antonin Bas <[email protected]>
Describe the problem/challenge you have
Helm chart is a popular way to package kubernetes apps, maybe we can support helm chart to allow some users with chart
experiences to eaily adapt antrea project.
Describe the solution you'd like
Provide helm chart with each release and publish it to officail helm chart repo
Anything else you would like to add?
Besides as an alternative way to distribute antrea, i'm not sure helm chart can provide additional features. Possible enhencement are:
The text was updated successfully, but these errors were encountered: