Open
Conversation
This file contains hidden or 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
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.
Implement _hw#1. This actually works but there are some differences between the instruction and my solution:
Instruction: Install Nginx as ingress controller. Nginx should be avialible on http://localhost:8080/
My solution: Using Ingress, we cannot specify spec.rules.host field as "localhost", cause it is like the exception host. Generally speaking, as I understood, using localhost is for debug/development thus a simple port forwarding does the trick. But I didn't find the solution how to automate
kubectl port-forwardcommand. That's why I've named host as "localhst" and it worked on the url: http://localhst , but in instruction nginx should be available on 8080 port. I've read that Ingress does not support 8080 port, only defaults 80 and 443, thats why I cannot use 8080 port. Also I can use Nodeport but It is not compatible with Ingress. If I try to use NodePort and make changes in /etc/hosts, I'll face the another problem: service's default node port range is 30000-33000, therefore I need to change it, but I cannot find the solution how to automate doing that just terminatingkubectl create -f <yml filename>command. That's why I can use port number in default range (30036). In this case it should work on http://localhst:30036/. I've chosen an Ingress option.To check this home task you need to add to /etc/hosts file the string below: