-
Notifications
You must be signed in to change notification settings - Fork 819
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
Move supported site K8s version to shortcodes #1917
Move supported site K8s version to shortcodes #1917
Conversation
Build Succeeded 👏 Build Id: 40b9342a-0f1b-42cc-9e3d-d08ee8d2dc42 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:
|
275cfa7
to
03e2510
Compare
Build Succeeded 👏 Build Id: 08955d6b-827b-4fef-bc60-dd21916a9431 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:
|
I'm kinda proud of this one - should hopefully save lots of time in the long run 😄 |
@@ -28,8 +28,8 @@ az group create --name $AKS_RESOURCE_GROUP --location $AKS_LOCATION | |||
|
|||
# Create the AKS cluster - this might take some time. Type 'az aks create -h' to see all available options | |||
|
|||
# The following command will create a four Node AKS cluster. Node size is Standard A1 v1 and Kubernetes version is 1.16.13. Plus, SSH keys will be generated for you, use --ssh-key-value to provide your values | |||
az aks create --resource-group $AKS_RESOURCE_GROUP --name $AKS_NAME --node-count 4 --generate-ssh-keys --node-vm-size Standard_A4_v2 --kubernetes-version 1.16.13 | |||
# The following command will create a four Node AKS cluster. Node size is Standard A1 v1 and Kubernetes version is {{% k8s-version %}}.13. Plus, SSH keys will be generated for you, use --ssh-key-value to provide your values |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to remember to change the minor versions too. Maybe make a short-code for aks-k8s-minor-version?
@@ -30,7 +30,7 @@ The following command starts a local minikube cluster via virtualbox - but this | |||
replaced by a [vm-driver](https://github.com/kubernetes/minikube#requirements) of your choice. | |||
|
|||
```bash | |||
minikube start --kubernetes-version v1.16.13 --vm-driver virtualbox | |||
minikube start --kubernetes-version v{{% k8s-version %}}.13 --vm-driver virtualbox |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minikube-k8s-minor-version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are good ideas. I'll make this change 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! I like it!
Implements two new shortcodes: * {{% k8s-version %}} - which outputs the currently supported version * {{% k8s-api href="#podtemplatespec-v1-core" %}} - which outputs the api reference url to the supported k8s version. These shortcode utilise the `HUGO_ENV` environment to determine if it should show the current K8s version, or the next - as it is only set to the value of "production" when it is generated for the release version of the agones.dev website. Also added updates to the release checklist to manage this as well. Ideally, this will remove lots of busy work of feature shortcoding a lot of content as we churn through Kubernetes versions. Long term, we may want to expand this to include separate tools for current and next full semver versions - i.e. rather than just 1.16 ➡ 1.17, but something like 1.16.3 ➡ 1.17.14. We cheat a little on this release as there is 1.16.13 and 1.17.13 released on both 1.16 and 1.17. Work on googleforgames#1824
03e2510
to
b26389e
Compare
b26389e
to
7350641
Compare
Build Failed 😱 Build Id: 2d465f9e-22df-4421-8770-9518053f22e5 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why the tests failed, but this looks great. It will definitely decrease our maintenance for each future k8s version upgrade. :)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build Failed 😱 Build Id: 70c14b1f-fd04-41fa-bef0-10e19797af71 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: d7a949dd-0997-44ec-994e-10728c21cc75 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:
|
What type of PR is this?
/kind documentation
What this PR does / Why we need it:
Implements two new shortcodes:
These shortcode utilise the
HUGO_ENV
environment to determine if it should show the current K8s version, or the next - as it is only set to the value of "production" when it is generated for the release version of the agones.dev website.Also added updates to the release checklist to manage this as well.
Ideally, this will remove lots of busy work of feature shortcoding a lot of content as we churn through Kubernetes versions.
Which issue(s) this PR fixes:
Work on #1824
Special notes for your reviewer:
Long term, we may want to expand this to include separate tools for current and next full semver versions - i.e. rather than just
1.16 ➡ 1.17, but something like 1.16.3 ➡ 1.17.14.
We cheat a little on this release as there is 1.16.13 and 1.17.13 released on both 1.16 and 1.17.