workshop icon indicating copy to clipboard operation
workshop copied to clipboard

Docker, Kubernetes and Gravity Trainings by Gravitational

Results 8 workshop issues
Sort by recently updated
recently updated
newest added

Replacing the deprecated syntax of the "kubectl run my-nginx --image=nginx --replicas=2 --port=80 --record" command with new format "kubectl create deployment my-nginx --image=nginx --replicas=2 --port=80"

The Gravity version used in Gravity 101 should be updated to the latest LTS version. https://gravitational.com/gravity/docs/changelog/

Current [Logging Workshop section](https://github.com/gravitational/workshop/blob/master/logging.md) pertains specifically to Gravity 5.5 and earlier. Logging stack has changed in 6.X+, training should be expanded to reflect the changes.

When following gravity101 training, it was noticed that the alpine pod get's installed in the kube-system namespace when using the v1 prebuilt version.

Current Monitoring/Alerts section pertains to Gravity 5.5 and earlier This task covers extending the training section to involve Gravity 6.X+ Also a new section should be added to the Monitoring/Alerts...

Add some discussion or section on log forwarder: - How log forwarder works - How to customize - How to troubleshoot (can be discussed in fire drills)

I would much prefer the k8s101.md version. So you can easily use an external registry. ``` k8s101.md:$ export registry="$(kubectl get svc/registry -ojsonpath='{.spec.clusterIP}'):5000" k8sprod.md:$ export registry=$(kubectl get svc/registry -ojsonpath="{.spec.clusterIP}") ```

Capturing some feedback from latest training workshop related to Docker 101 section: *Incorporate best practices for writing dockerfile *Developer experience, at what point to introduce docker at your company (may...