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

Integrated Helm into the build and development system #170

Merged
merged 1 commit into from
Apr 10, 2018

Conversation

markmandel
Copy link
Member

This removes the sed based templating and replaces it with a helm based workflow. All the make commands have stayed exactly the same.

This also moves the existing 0.1 release helm chat to the 0.2 development chart, and includes the features that were otherwise missing for 0.2

If you have an existing development cluster, it may be easiest to delete them and recreate them, as the tooling will install helm automatically now on cluster creation.

I also snuck in some small Kubernetes 1.9.x upgrades as well.

Parent ticket: #101

This removes the `sed` based templating and replaces it with a
helm based workflow. All the `make` commands have stayed exactly
the same.

This also moves the existing 0.1 release helm chat to the 0.2
development chart, and includes the features that were otherwise
missing for 0.2

If you have an existing development cluster, it may be easiest
to delete them and recreate them, as the tooling will install
helm automatically now on cluster creation.

I also snuck in some small Kubernetes 1.9.x upgrades as well.

Parent ticket: googleforgames#101
@markmandel markmandel added the area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. label Apr 9, 2018
@markmandel markmandel added this to the 0.2 milestone Apr 9, 2018
@markmandel markmandel requested a review from cyriltovena April 9, 2018 22:31
@markmandel
Copy link
Member Author

/cc @fooock

@agones-bot
Copy link
Collaborator

Build Succeeded 👏

Build Id: e66af0ab-4b49-4ee6-a1e1-1601c477bdcd

The following development artifacts have been built, and will exist for the next 30 days:

markmandel added a commit to markmandel/agones that referenced this pull request Apr 9, 2018
This implements a `make gen-install` target that will generate the
install.yaml via `helm template`. This also extends `make test`
to have a test to ensure that the `install.yaml` is always kept
up to sync with the Helm chart, otehrwise the build will fail.

This does remove the explicit permissions for RBAC, but we don't
have a specific need for them right now, so I feel it's worth the
sacrifice to ensure these two configuration options stay in sync.

Blocks on googleforgames#170, Parent ticket: googleforgames#101
Copy link
Collaborator

@cyriltovena cyriltovena left a comment

Choose a reason for hiding this comment

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

Looks good to me,

We loose the ability to use funky image tag but it's really minor and not needed.

@cyriltovena cyriltovena merged commit 794dcdb into googleforgames:master Apr 10, 2018
@markmandel markmandel deleted the feature/helm-0.2 branch April 10, 2018 14:59
markmandel added a commit to markmandel/agones that referenced this pull request Apr 10, 2018
This implements a `make gen-install` target that will generate the
install.yaml via `helm template`. This also extends `make test`
to have a test to ensure that the `install.yaml` is always kept
up to sync with the Helm chart, otehrwise the build will fail.

This does remove the explicit permissions for RBAC, but we don't
have a specific need for them right now, so I feel it's worth the
sacrifice to ensure these two configuration options stay in sync.

Blocks on googleforgames#170, Parent ticket: googleforgames#101
markmandel added a commit to markmandel/agones that referenced this pull request Apr 10, 2018
This implements a `make gen-install` target that will generate the
install.yaml via `helm template`. This also extends `make test`
to have a test to ensure that the `install.yaml` is always kept
up to sync with the Helm chart, otehrwise the build will fail.

This does remove the explicit permissions for RBAC, but we don't
have a specific need for them right now, so I feel it's worth the
sacrifice to ensure these two configuration options stay in sync.

Blocks on googleforgames#170, Parent ticket: googleforgames#101
markmandel added a commit to markmandel/agones that referenced this pull request Apr 10, 2018
This implements a `make gen-install` target that will generate the
install.yaml via `helm template`. This also extends `make test`
to have a test to ensure that the `install.yaml` is always kept
up to sync with the Helm chart, otehrwise the build will fail.

This does remove the explicit permissions for RBAC, but we don't
have a specific need for them right now, so I feel it's worth the
sacrifice to ensure these two configuration options stay in sync.

Blocks on googleforgames#170, Parent ticket: googleforgames#101
markmandel added a commit to markmandel/agones that referenced this pull request Apr 10, 2018
This implements a `make gen-install` target that will generate the
install.yaml via `helm template`. This also extends `make test`
to have a test to ensure that the `install.yaml` is always kept
up to sync with the Helm chart, otehrwise the build will fail.

This does remove the explicit permissions for RBAC, but we don't
have a specific need for them right now, so I feel it's worth the
sacrifice to ensure these two configuration options stay in sync.

Blocks on googleforgames#170, Parent ticket: googleforgames#101
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-tools Development tooling. I.e. pretty much everything in the `build` directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants