update c.pod-design.md : test deployment from within a pod #303
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
That's good, it teaches how to use busybox to debug connection issues from inside the cluster which is a good to know for any CKAD candidate. |
kaizendae
approved these changes
Nov 1, 2022
Add a better one liner solution instead of having a shell to the busybox pod and running the command
dgkanatsios
approved these changes
Mar 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
In the Pod Design section in the last exercice : https://github.com/dgkanatsios/CKAD-exercises/blob/main/c.pod_design.md#implement-canary-deployment-by-running-two-instances-of-nginx-marked-as-versionv1-and-versionv2-so-that-the-load-is-balanced-at-75-25-ratio
In the solution it is needed to check if the deployment was successful by using the command :
curl $(kubectl get svc my-app-svc -o jsonpath="{.spec.clusterIP}"), however this command does not work if you don't have a nodePort Service to expose it to your local machine.My suggestion is to test the deployment from whitin a pod by using a busyBox image and the
wgetcommand.This is also a solution to the issue : #281