Your videos excellent and error-free sir....Thanx for ur commitment to teach us....we expect some more videos of various other CI/CD tools
@PraveenakumaraPY Жыл бұрын
Well explain sir..keep updating more video..sir kubernet videos please sir
@alberthien3720 Жыл бұрын
Great job Yunus , keep it up ❤
@Deepakverma-cd3md8 ай бұрын
Hi, I didn't get why you updated the env. variable value just after the creation of the cluster.
@UnusAWS8 ай бұрын
If you're executing the script in a subshell or a separate shell session (for example, by running ./script.sh), the environment variable won't persist in your current shell session. Hence you need to do the env variable setup once again. Without this env. variable some of the subsequent commands won't work.
@ancientpast5 ай бұрын
sir pods are created in launched instance
@girishfury2630Ай бұрын
i want to use ingress controller but the problem here is it is creating classic load balancer.. it is working fine bt i am struggling with using ACM certs in path based routing.. not sure wht to do
@sumitraut-dr8gm7 ай бұрын
if i dont want to create worker and master nodes should i skip the step that are in vi and go with only one node
@kishorevunna-m6w8 ай бұрын
once I installed the Kubernetes cluster, I used kubectl apply -f pod.yaml, then its asking for userid and pwd, where should I get it from
@UnusAWS8 ай бұрын
To create a set of access key id and secret access key, you can go to IAM > IAM Dashboard. Click on ‘My Security Credentials’ under 'Quick links'. Under ‘Security Credentials’ page, click on ‘AWS IAM Credentials’. Under 'access keys', click on ‘create access key’. Under use case, choose ‘CLI’. Give any description tag value . Click ‘Create access key’. You can copy the access key id and secret access key to a notepad. Or you can download the same into a csv file.