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

Adds instructions for adding and removing field from a CRD #3913

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

igooch
Copy link
Collaborator

@igooch igooch commented Jul 18, 2024

What type of PR is this?

/kind documentation

What this PR does / Why we need it:

Adds instructions necessary for adding and removing a field from a CRD, so that the CRD will be compatible across upgrades.

Which issue(s) this PR fixes:

Closes #3771

Special notes for your reviewer:

@github-actions github-actions bot added kind/documentation Documentation for Agones size/S labels Jul 18, 2024
@agones-bot
Copy link
Collaborator

Build Succeeded 👏

Build Id: 93d5398a-ca56-4b4a-a846-d3be80c9e763

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

A preview of the website (the last 30 builds are retained):

To install this version:

  • git fetch https://github.com/googleforgames/agones.git pull/3913/head:pr_3913 && git checkout pr_3913
  • helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.43.0-dev-c303b36-amd64

@@ -3,3 +3,69 @@
This chart installs the Agones application and defines deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

See [Install Agones using Helm](https://agones.dev/site/docs/installation/install-agones/helm/) for installation and configuration instructions.

## Development Work on Agones Custom Resource Definitions (CRDs)
Copy link
Collaborator

Choose a reason for hiding this comment

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

This feels like a really weird place - I feel like this is a little more user-centric README in general.

I'm struggling to come up with a better place, though. @markmandel ?

Copy link
Member

Choose a reason for hiding this comment

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

Agreed, this should be in one of the files listed here: https://github.com/googleforgames/agones?tab=readme-ov-file#development-and-contribution

Quite possibly https://github.com/googleforgames/agones/blob/main/CONTRIBUTING.md since it has all our other style guides.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Would it make sense to follow the same pattern as the SDK and link to the ReadMe from the contributing page?

For Agones client SDK development refer to [Developing, Testing, and Building Agones Client SDKs](sdks/README.md).

Copy link
Member

Choose a reason for hiding this comment

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

This has both a style guide as well as a development guide - which is not a bad thing, but we've never quite done it like this, so it's a little trickier to put in an existing place.

Would it make sense to follow the same pattern as the SDK and link to the ReadMe from the contributing page?

What README would you put it in? There isn't really a spot that I can think of. We could always add a docs folder to https://github.com/googleforgames/agones/tree/main/build though? But open to your suggestions.

It could possibly be a section in https://github.com/googleforgames/agones/blob/main/build/README.md#testing-and-building ?

Or take a stab at taking apart https://github.com/googleforgames/agones/blob/main/build/README.md into some sub-sectioned files, even it's just some basics - and it could be the beginning of making that a better experience - right now it's not terrific.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

What README would you put it in?

The one it's in now -- agones/install/helm/agones/README.md. I figured it made the most sense since that's where the installation files are, and sparse readme already existed. Or we could add a readme into the agones/install/helm/agones/templates/crds directory where the CRDs are? I'm not sure it belongs in the testing-and-building section, simply because most people won't be amending the CRDs.

Or take a stab at taking apart https://github.com/googleforgames/agones/blob/main/build/README.md into some sub-sectioned files

We should probably create a new GitHub issue for this.

@agones-bot
Copy link
Collaborator

Build Succeeded 🥳

Build Id: 6af5ca43-53b4-4cac-aaf1-7ba559f5175f

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

A preview of the website (the last 30 builds are retained):

To install this version:

git fetch https://github.com/googleforgames/agones.git pull/3913/head:pr_3913 && git checkout pr_3913
helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.43.0-dev-f5997d9

install/helm/agones/README.md Outdated Show resolved Hide resolved
@@ -3,3 +3,69 @@
This chart installs the Agones application and defines deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

See [Install Agones using Helm](https://agones.dev/site/docs/installation/install-agones/helm/) for installation and configuration instructions.

## Development Work on Agones Custom Resource Definitions (CRDs)
Copy link
Member

Choose a reason for hiding this comment

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

This has both a style guide as well as a development guide - which is not a bad thing, but we've never quite done it like this, so it's a little trickier to put in an existing place.

Would it make sense to follow the same pattern as the SDK and link to the ReadMe from the contributing page?

What README would you put it in? There isn't really a spot that I can think of. We could always add a docs folder to https://github.com/googleforgames/agones/tree/main/build though? But open to your suggestions.

It could possibly be a section in https://github.com/googleforgames/agones/blob/main/build/README.md#testing-and-building ?

Or take a stab at taking apart https://github.com/googleforgames/agones/blob/main/build/README.md into some sub-sectioned files, even it's just some basics - and it could be the beginning of making that a better experience - right now it's not terrific.

@agones-bot
Copy link
Collaborator

Build Succeeded 🥳

Build Id: 3df5a1cc-1e41-44b4-baf2-72dae163f00e

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

A preview of the website (the last 30 builds are retained):

To install this version:

git fetch https://github.com/googleforgames/agones.git pull/3913/head:pr_3913 && git checkout pr_3913
helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.43.0-dev-569d082

@agones-bot
Copy link
Collaborator

Build Succeeded 🥳

Build Id: e007e125-cc64-495d-a112-12d62df984ef

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

A preview of the website (the last 30 builds are retained):

To install this version:

git fetch https://github.com/googleforgames/agones.git pull/3913/head:pr_3913 && git checkout pr_3913
helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.44.0-dev-9dfbd81

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Documentation for Agones size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In-place Agones Upgrades: Storage Compatibility
5 participants