Git Product home page Git Product logo

azure-aks-kubernetes-masterclass's People

Contributors

stacksimplify avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

azure-aks-kubernetes-masterclass's Issues

Helm INSTALLATION FAILED

Hi There,
I am following your document and every time getting below issue while executing below commonds
helm install ingress-nginx ingress-nginx/ingress-nginx
--namespace ingress-basic
--set controller.replicaCount=2
--set controller.nodeSelector."beta.kubernetes.io/os"=linux
--set defaultBackend.nodeSelector."beta.kubernetes.io/os"=linux
--set controller.service.externalTrafficPolicy=Local
--set controller.service.loadBalancerIP="REPLACE_STATIC_IP" // I have replaced with my aks public ip

Error: INSTALLATION FAILED: failed pre-install: 1 error occurred:
* timed out waiting for the condition

helm.go:84: [debug] failed pre-install: 1 error occurred:
* timed out waiting for the condition

INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:154
github.com/spf13/cobra.(*Command).execute
github.com/spf13/[email protected]/command.go:940
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/[email protected]/command.go:1068
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/[email protected]/command.go:992
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:267
runtime.goexit
runtime/asm_arm64.s:1197

chapter 56

Yaml file

  • name: DB_USERNAME
    value: "dbadmin"

mysql:5.7.22 -> mysql:5.7.40

Chapter 55

kubectl run -it --rm --image=mysql:5.7.40 --restart=Never mysql-client -- mysql -h akswebappdb1304.mysql.database.azure.com -u dbadmin -pRedhat1449

Module 14 cluster-issuer.yml

server needs changing from:
server: https://acme-v02.api.letsencrypt.org/directory
to:
server: https://acme-staging-v02.api.letsencrypt.org/directory
for the staging environment

Nginx pods are pending in virtual nodes

https://github.com/stacksimplify/azure-aks-kubernetes-masterclass/tree/master/17-Azure-VirtualNodes-for-AKS/17-01-Azure-VirtualNodes-Basics

I have created a cluster with virtual node and ran above example.
I can see Nginx pods, but they are getting stuck in pending status.

$ kubectl get pods

NAME                                     READY   STATUS    RESTARTS   AGE
app1-nginx-deployment-6bbd5745cc-p64xs   0/1     Pending   0          3m30s
app1-nginx-deployment-6bbd5745cc-xnpl9   0/1     Pending   0          3m30s

$ kubectl get pods -o wide

NAME                                     READY   STATUS    RESTARTS   AGE     IP       NODE     NOMINATED NODE   READINESS GATES
app1-nginx-deployment-6bbd5745cc-p64xs   0/1     Pending   0          4m47s   <none>   <none>   <none>           <none>
app1-nginx-deployment-6bbd5745cc-xnpl9   0/1     Pending   0          4m47s   <none>   <none>   <none>           <none>

$ kubectl get nodes

NAME                                STATUS   ROLES   AGE   VERSION
aks-agentpool-36277780-vmss000002   Ready    agent   38m   v1.24.9
virtual-node-aci-linux              Ready    agent   36m   v1.19.10-vk-azure-aci-1.4.8

I tried to describe pods.

kubectl describe pod app1-nginx-deployment-6bbd5745cc-wj7rb

Name:             app1-nginx-deployment-6bbd5745cc-wj7rb
Namespace:        default
Priority:         0
Service Account:  default
Node:             <none>
Labels:           app=app1-nginx
                  pod-template-hash=6bbd5745cc
Annotations:      <none>
Status:           Pending
IP:               
IPs:              <none>
Controlled By:    ReplicaSet/app1-nginx-deployment-6bbd5745cc
Containers:
  app1-nginx:
    Image:        stacksimplify/kube-nginxapp1:1.0.0
    Port:         80/TCP
    Host Port:    0/TCP
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-tp6k5 (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  kube-api-access-tp6k5:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
                             kubernetes.io/role=agent
                             type=virtual-kubelet
Tolerations:                 azure.com/aci:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
                             virtual-kubelet.io/provider op=Exists
Events:
  Type     Reason             Age   From                Message
  ----     ------             ----  ----                -------
  Warning  FailedScheduling   42s   default-scheduler   0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
  Normal   NotTriggerScaleUp  37s   cluster-autoscaler  pod didn't trigger scale-up: 1 node(s) didn't match Pod's node affinity/selector

How to redirect the port in ingress?

Hello Sir,

I have recently registered to your udemy course.
In that ingress section, you added routes to multiple application but all having container port as 80 only.
With Ingress, our application is using port 18170.
But with ingress, even if I keep servicePort as 18170, it is not working.

Can you create a video on that and to your course.

Like, adding routes to multiple apps with different ports for their service.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.