ContainerSolutions / ContainerSolutions/kubernetes-examples
Automate the release process
- Dominant language
- Shell
- Stars
- 1.4k
- Forks
- 309
- PR merge metrics
- No merged PRs in 30d
Description
Hi there.
We have found some differences between the main branch and the released github pages with the resource examples.
For example: [Ingress resource example page](https://k8s-examples.container-solutions.com/examples/Ingress/Ingress.html) vs [Ingress resource example in master branch](https://github.com/ContainerSolutions/kubernetes-examples/blob/master/Ingress/ingress.yaml). Latest release done was done in May 2021.
This ticket is to rethink the release process and automate it if viable.
Contributor guide
Research direction
Start by comparing the Ingress/ingress.yaml example in the master branch with its released GitHub Pages version at the linked URL, then inspect how the current release process publishes resource examples. Define an automated path that keeps released pages synchronized with the main branch and verify it against the example differences described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100