feat: add helm chart #379
feat: add helm chart #379
Conversation
dirien
force-pushed
the
helm
branch
6 times, most recently
from
31c20e0
to
aeccd81
Compare
There was a problem hiding this comment.
Overall this looks great! Most things are not blocking but finding a streamlined way to make things consistent between chart and no-chart would help. Maybe we just need to set expectations to transition quickly to chart-first. I will let @squaremo share his thoughts.
|
For the record, my feedback was
|
dirien
force-pushed
the
helm
branch
4 times, most recently
from
8527ce2
to
6dd2188
Compare
|
Is this a dupe of #261? |
|
hi @squaremo, I think I close this one and make one Chart in my own orga? Wdyt? |
AaronFriel
dismissed
their stale review
Meant to comment, not approve, this isn't a repository I own
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
dirien
requested review from
AaronFriel and
viveklak
and removed request for
squaremo and
viveklak
This commit includes a new directory, helm, which contains the necessary files for deploying the application to Kubernetes clusters using the Helm package manager. The chart includes: - Deployment - Role and role binding - Service account - CRD definition Resources for the Pulumi Kubernetes Operator, as well as the configurable values file (values.yaml) for specifying the deployment of the Operator. This change will allow our customers to more easily manage and deploy the Operator on various Kubernetes environments, streamlining the process and reducing the potential for errors. Signed-off-by: Engin Diri <engin.diri@ediri.de>
This commit introduces a series of GitHub workflows to the codebase, which will be used to automate various tasks related to continuous integration and deployment. These workflows are defined in the `.github/workflows` directory, and include the following: - `ct-linting-and-testing.yaml`: This workflow is triggered on pull requests, and is responsible for linting and testing the chart to ensure that it is in a releasable state. - `chart-publish.yaml`: This workflow is triggered on the main branch only when changes are detected in the chart directory, and is responsible for releasing the chart as traditional bundle and OCI artefact. - Diverse linter configuration files to tune the linting process to our needs. Overall, these workflows will help to streamline the development process of the Helm charts and ensure that templating code is always in a deployable state. Signed-off-by: Engin Diri <engin.diri@ediri.de>
Signed-off-by: Engin Diri <engin.diri@ediri.de>
Signed-off-by: Engin Diri <engin.diri@ediri.de>
Signed-off-by: Engin Diri <engin.diri@ediri.de>
Proposed changes
Hi,
this PR adds the creation of Helm chart for the Pulumi operator.
The helm chart can be deployed in two ways:
It uses:
Related issues (optional)