Skip to content
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

Making the kustomization deployment story better #624

Merged
merged 20 commits into from
Nov 30, 2021

Conversation

NissesSenap
Copy link
Collaborator

Description

Making the kustomization deployment story better by having a easy to use kustomization file that is up to date.
Will also generate specific folders for tagged releases.

From now on using the generated yaml in the e2e scripts to make sure that it tests what the kubernetes users will use to deploy the operator.

Relevant issues/tickets

Partly solves #623
When this get's merged we will need to remove the old deployment files for v3.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • This change requires a documentation update
  • I have added tests that prove my fix is effective or that my feature works
  • I have added a test case that will be used to verify my changes
  • Verified independently on a cluster by reviewer

Verification steps

Run the e2e test

Edvin Norling added 15 commits November 24, 2021 19:52
This should help users easier be able to setup the operator.
Instead of having to create some advanced logic the users can point
on these folders with there own kustomization files.
This to make it easier when separeting the kustomization logic
Specify ./bin/manager in .gitignore
Adding namespace in manifests.
This way we can generate manifests files that can even be applied using
kubectl apply -f, that points directly to the correct namespace
without any kustomization logic.
I can't make the generated yaml files look good enough any way.
So people will have to use kustomization to apply
It won't be as visiable but before making a commit the developer should run
make test and nothing should be changed in the repo.
This will also look for changes in kustomization mainfest folders
It's a bit painful to do this without getting the old versions.
I will try in a seperate PR to make sure there are in line
This shoulden't create issues in test make command
This way a person making a release can use the makefile easily as well.
@NissesSenap
Copy link
Collaborator Author

When this is merged my plan is to create a separate PR that will use the manifests files from v4.0.2 tag and use this sciprt to generate kustomization fils for it.

HVBE
HVBE previously approved these changes Nov 29, 2021
Copy link
Collaborator

@HVBE HVBE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! tested it out locally, works really nice 👍

This pipeline now checks for changes in the repo and that is why the
pipeline fails
@NissesSenap NissesSenap merged commit f2a60fa into grafana:master Nov 30, 2021
@NissesSenap NissesSenap deleted the kustomize_install branch November 30, 2021 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants