search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

Successful install but pods crashing. #127

Closed henmo09 closed 3 years ago

henmo09 commented 3 years ago

ansible-playbook -e BASE_DIR=$HOME/project/viya4-deployment -e CONFIG=$HOME/project/viya4-deployment/ansible-vars.yaml -e TFSTATE=$HOME/project/viya4-iac-azure/terraform.tfstate -e JUMP_SVR_PRIVATE_KEY=$HOME/.ssh/id_rsa playbooks/playbook.yaml --tags "baseline,viya,install"

pod-describe pods-crashing what we are missing here!!! vents: Type Reason Age From Message

Normal Scheduled 9m35s default-scheduler Successfully assigned viya4-frg-v1/sas-analytics-components-65cf89944f-pqcbj to aks-stateless-38049675-vmss000000 Normal Pulling 9m32s kubelet Pulling image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.7.2-20201208.1607438373197" Normal Pulled 9m1s kubelet Successfully pulled image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.7.2-20201208.1607438373197" in 31.323353552s Normal Pulled 8m19s (x3 over 8m59s) kubelet Container image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.7.2-20201208.1607438373197" already present on machine Normal Started 8m18s (x4 over 9m1s) kubelet Started container sas-certframe Normal Created 7m27s (x5 over 9m1s) kubelet Created container sas-certframe Warning BackOff 5m33s (x12 over 8m57s) kubelet Back-off restarting failed container NAME READY STATUS RESTARTS AGE openldap-7d5d969849-t2mmz 1/1 Running 0 9m55s sas-analytics-components-65cf89944f-pqcbj 0/1 Init:CrashLoopBackOff 6 9m55s sas-analytics-events-5575d8c5cc-68ngv 0/1 Init:CrashLoopBackOff 6 9m55s sas-analytics-services-2-59dd7d99c9-gs2jr 0/1 Init:CrashLoopBackOff 6 9m55s sas-analytics-services-85dcc8d7d5-f7nqw 0/1 Init:CrashLoopBackOff 6 9m55s sas-annotations-796bd475b4-lnfrz 0/1 Init:CrashLoopBackOff 6 9m55s sas-app-registry-65486dcdbf-dlf89 0/1 Init:CrashLoopBackOff 6 9m55s sas-arke-85d8d9b644-8v6zm 0/1 Init:CrashLoopBackOff 6 9m54s sas-audit-dd68f8d68-fsgzz 0/1 Init:CrashLoopBackOff 6 9m54s sas-authorization-5476bb7464-jmdkp 0/1 Init:CrashLoopBackOff 6 9m54s sas-batch-6757578745-zh85f 0/1 Init:CrashLoopBackOff 6 9m54s sas-business-rules-services-79b7b59486-r55zn 0/1 Init:CrashLoopBackOff 6 9m54s sas-cachelocator-0 0/1 Init:CrashLoopBackOff 6 9m50s sas-cacheserver-0 0/1 Init:CrashLoopBackOff 6 9m50s sas-cacheserver-1 0/1 Init:CrashLoopBackOff 6 9m50s sas-cas-administration-599cb54b4c-rpvpw 0/1 Init:CrashLoopBackOff 6 9m54s sas-cas-control-85f577f5cf-rqrp5 0/1 Init:CrashLoopBackOff 6 9m53s sas-cas-operator-d48db9b5-x98lg 0/1 Init:CrashLoopBackOff 6 9m53s sas-comments-76fd6bbcb6-2r9ck 0/1 Init:CrashLoopBackOff 6 9m53s sas-compute-58c9b6b49b-z8nq8 0/1 Init:CrashLoopBackOff 6 9m53s sas-config-reconciler-76fbd8668f-tqkgv 0/1 Init:CrashLoopBackOff 6 9m53s sas-configuration-59dd578765-9clhb 0/1 Init:CrashLoopBackOff 6 9m52s sas-connect-6b45dcc465-jbmqm 0/1 Init:CrashLoopBackOff 6 9m52s sas-connect-spawner-c5d5c85b6-hlzfl 0/1 Init:CrashLoopBackOff 6 9m52s sas-consul-server-0 0/1 Init:CrashLoopBackOff 6 9m50s sas-consul-server-1 0/1 Init:CrashLoopBackOff 6 9m50s sas-consul-server-2 0/1 Init:CrashLoopBackOff 6 9m50s sas-conversation-designer-app-746c87c6c-8zmnt 0/1 Init:CrashLoopBackOff 6 9m52s sas-credentials-7b9659949c-rqllc 0/1 Init:CrashLoopBackOff 6 9m52s sas-crossdomainproxy-85bcdcdd8d-9rfg8 0/1 Init:CrashLoopBackOff 6 9m52s sas-data-explorer-app-97f7cb46b-x7c9n 0/1 Init:CrashLoopBackOff 6 9m51s sas-data-flows-6b76cb9c59-rqkjv 0/1 Init:CrashLoopBackOff 6 9m51s sas-data-mining-models-5bc48d9cd7-sb944 0/1 Init:CrashLoopBackOff 6 9m51s sas-data-mining-project-settings-794c55ff88-gnxgc 0/1 Init:CrashLoopBackOff 6 9m51s sas-data-mining-results-dcdf7679d-wb7zj 0/1 Init:CrashLoopBackOff 6 9m51s sas-data-mining-services-774c856b5d-mncl8 0/1 Init:CrashLoopBackOff 6 9m50s sas-data-plans-5cf448bd66-rtct5 0/1 Init:CrashLoopBackOff 6 9m50s sas-data-profiles-65fc95dcc4-t4gq4 0/1 Init:CrashLoopBackOff 6 9m50s sas-data-quality-services-86bb4679b7-t5k5f 0/1 Init:CrashLoopBackOff 6 9m50s sas-data-server-utility-7698c66768-49lk5 0/1 Init:CrashLoopBackOff 6 9m50s sas-data-sources-97d8f56dd-g9nxp 0/1 Init:CrashLoopBackOff 6 9m49s sas-data-studio-app-588fd4fdb8-svrf7 0/1 Init:CrashLoopBackOff 6 9m49s sas-decision-manager-app-7bcbf9dfb7-nsphp 0/1 Init:CrashLoopBackOff 6 9m49s sas-decisions-definitions-68bc75b446-jbnqt 0/1 Init:CrashLoopBackOff 6 9m48s sas-deployment-data-84fbddbdc6-5lhxg 0/1 Init:CrashLoopBackOff 6 9m48s sas-device-management-8596d998df-jklpn 0/1 Init:CrashLoopBackOff 6 9m48s sas-drive-app-56f89fc5f-f62wm 0/1 Init:CrashLoopBackOff 6 9m48s sas-environment-manager-app-6c4f656898-grx2x 0/1 Init:CrashLoopBackOff 6 9m48s sas-esp-operator-8c5f5cb89-z6w62 0/1 Init:CrashLoopBackOff 6 9m48s sas-event-stream-manager-app-66c675d7-s8j8n 0/1 Init:CrashLoopBackOff 6 9m47s sas-event-stream-processing-metering-app-7bc945c68f-42x2k 0/1 Init:CrashLoopBackOff 6 9m47s sas-event-stream-processing-streamviewer-app-55cbd67d9f-8h4bt 0/1 Init:CrashLoopBackOff 6 9m47s sas-event-stream-processing-studio-app-76f7588b87-78nvt 0/1 Init:CrashLoopBackOff 6 9m47s sas-files-59f9fd4777-hqq9j 0/1 Init:CrashLoopBackOff 6 9m47s sas-folders-75b5b6575b-97t8h 0/1 Init:CrashLoopBackOff 6 9m46s sas-fonts-7dd69b8c5c-xk9qf 0/1 Init:CrashLoopBackOff 6 9m46s sas-forecasting-comparison-8494bd4587-7ftw5 0/1 Init:CrashLoopBackOff 6 9m46s sas-forecasting-events-6b8846f57f-t5hzr 0/1 Init:CrashLoopBackOff 6 9m46s sas-forecasting-exploration-5b7b4bc6dd-676x4 0/1 Init:CrashLoopBackOff 6 9m46s sas-forecasting-filters-58578b746b-2vv4p 0/1 Init:CrashLoopBackOff 6 9m46s sas-forecasting-pipelines-6d9b9d7484-bxlql 0/1 Init:CrashLoopBackOff 6 9m45s sas-forecasting-services-6fb7fbd4d6-5twtj 0/1 Init:CrashLoopBackOff 6 9m45s sas-geo-enrichment-774cc4988d-z66b2 0/1 Init:CrashLoopBackOff 6 9m45s sas-graph-builder-app-689f984c97-9nw7v 0/1 Init:CrashLoopBackOff 6 9m45s sas-graph-templates-847f8689f9-xwszh 0/1 Init:CrashLoopBackOff 6 9m45s sas-identities-5949c48777-vt4cp 0/1 Init:CrashLoopBackOff 6 9m44s sas-import-9-679cccdfdd-vrdgh 0/1 Init:CrashLoopBackOff 6 9m44s sas-job-execution-76897467ff-wt7w2 0/1 Init:CrashLoopBackOff 6 9m44s sas-job-execution-app-cb5fd86c5-c5ks2 0/1 Init:CrashLoopBackOff 6 9m44s sas-job-flow-scheduling-678f5b797-tzd8t 0/1 Init:CrashLoopBackOff 6 9m44s sas-launcher-596c8c7d94-zjjk8 0/1 Init:CrashLoopBackOff 6 9m43s sas-lineage-app-5d47b599f4-b6r9k 0/1 Init:CrashLoopBackOff 6 9m43s sas-links-6f64c767-nfwv2 0/1 Init:CrashLoopBackOff 6 9m43s sas-localization-6489d57c45-f9tv4 0/1 Init:CrashLoopBackOff 6 9m43s sas-logon-app-764795d975-t5ff6 0/1 Init:CrashLoopBackOff 6 9m43s sas-mail-86759b6647-nng2t 0/1 Init:CrashLoopBackOff 6 9m43s sas-maps-5689cb79c9-m94xs 0/1 Init:CrashLoopBackOff 6 9m42s sas-microanalytic-score-66db4d8f5d-f6rvv 0/1 Init:CrashLoopBackOff 6 9m42s sas-model-management-749f985c95-dkkxw 0/1 Init:CrashLoopBackOff 6 9m42s sas-model-manager-app-5985f9c7fd-jtkq5 0/1 Init:CrashLoopBackOff 6 9m42s sas-model-publish-5b8b97d7d6-z6rcl 0/1 Init:CrashLoopBackOff 6 9m42s sas-model-repository-5c8cfdd44c-xwtms 0/1 Init:CrashLoopBackOff 6 9m41s sas-model-studio-app-77b95bf6bb-nn688 0/1 Init:CrashLoopBackOff 6 9m41s sas-natural-language-conversations-6fbd46688f-x7pf8 0/1 Init:CrashLoopBackOff 6 9m41s sas-natural-language-generation-6686b5779d-mmhfh 0/1 Init:CrashLoopBackOff 6 9m41s sas-natural-language-understanding-f577bb4c8-5rswd 0/1 Init:CrashLoopBackOff 6 9m41s sas-notifications-5c4cb6698f-vdsg5 0/1 Init:CrashLoopBackOff 6 9m40s sas-preferences-7b4cc548-nb8t8 0/1 Init:CrashLoopBackOff 6 9m40s sas-prepull-6p5vg 0/1 Init:ImagePullBackOff 0 9m46s sas-projects-5b9789cf59-cqvlw 0/1 Init:CrashLoopBackOff 6 9m40s sas-rabbitmq-server-0 0/1 Init:CrashLoopBackOff 6 9m50s sas-rabbitmq-server-1 0/1 Init:CrashLoopBackOff 6 9m50s sas-rabbitmq-server-2 0/1 Init:CrashLoopBackOff 6 9m50s sas-readiness-749b97b9dc-c4mfx 0/1 Init:CrashLoopBackOff 6 9m40s sas-relationships-78964b7d7c-z49mc 0/1 Init:CrashLoopBackOff 6 9m40s sas-report-distribution-7b979df8d9-l69xz 0/1 Init:CrashLoopBackOff 6 9m39s sas-report-execution-f48dbd5ff-5f7bw 0/1 Init:CrashLoopBackOff 6 9m39s sas-report-renderer-b4b6b7487-zbq5v 0/1 Init:CrashLoopBackOff 6 9m39s sas-report-services-group-595ff5bdfb-8pstj 0/1 Init:CrashLoopBackOff 6 9m39s sas-scheduler-5c5794c77f-76sjz 0/1 Init:CrashLoopBackOff 6 9m39s sas-score-definitions-68cc67c479-pwlwv 0/1 Init:CrashLoopBackOff 6 9m38s sas-score-execution-9fb6ddf55-w67m5 0/1 Init:CrashLoopBackOff 6 9m38s sas-search-64d6f9699d-tmzkm 0/1 Init:CrashLoopBackOff 6 9m38s sas-studio-app-fb4d6f488-59x95 0/1 Init:CrashLoopBackOff 6 9m38s sas-subject-contacts-7458f75b4c-7tkjx 0/1 Init:CrashLoopBackOff 6 9m38s sas-templates-59c6c6588d-8fn58 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-analytics-67bc677c44-hjcwj 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-cas-data-management-776b9dd85c-gslx2 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-categorization-7bf7dcd44b-pdg4v 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-concepts-84f579ff95-g64zm 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-parsing-55df7fd5bd-lbk2k 0/1 Init:CrashLoopBackOff 6 9m37s sas-text-sentiment-7496c5d875-g4j7f 0/1 Init:CrashLoopBackOff 6 9m36s sas-text-topics-6b49568748-xlh9c 0/1 Init:CrashLoopBackOff 6 9m36s sas-theme-content-77f58dcd7b-22zx4 0/1 Init:CrashLoopBackOff 6 9m36s sas-theme-designer-app-79dbf9bb49-8zqh7 0/1 Init:CrashLoopBackOff 6 9m36s sas-themes-8b8f7fb89-ddkgp 0/1 Init:CrashLoopBackOff 6 9m36s sas-thumbnails-66bbfcfd6-dbw4s 0/1 Init:CrashLoopBackOff 6 9m35s sas-topic-management-9748f7fc4-r8shl 0/1 Init:CrashLoopBackOff 6 9m35s sas-transfer-58d75dfb49-qs5h5 0/1 Init:CrashLoopBackOff 6 9m35s sas-transformations-5c8bbc9768-nt5cn 0/1 Init:CrashLoopBackOff 6 9m35s sas-types-896c895bf-dpc9d 0/1 Init:CrashLoopBackOff 6 9m35s sas-visual-analytics-administration-856b759f4f-5hdfg 0/1 Init:CrashLoopBackOff 6 9m34s sas-visual-analytics-app-5bd959bc47-vccrr 0/1 Init:CrashLoopBackOff 6 9m34s sas-web-data-access-f65b58989-47cx9 0/1 Init:CrashLoopBackOff 6 9m34s sas-workflow-7d4cf68d64-d2pxq 0/1 Init:CrashLoopBackOff 6 9m34s sas-workflow-definition-history-77c79b5bfc-xdxbn 0/1 Init:CrashLoopBackOff 6 9m34s sas-workflow-manager-app-6bbd577b57-l9b4d 0/1 Init:CrashLoopBackOff 6 9m33s root@henmo:~/project/viya4-deployment#

VARIABLES file:

root@henmo:~/project/viya4-deployment# cat ansible-vars.yaml

Cluster

NAMESPACE: viya4-frg-v1

MISC

DEPLOY: true # Set to false to stop at generating the manifest LOADBALANCER_SOURCE_RANGES: ['0.0.0.0/0']

Storage

V4_CFG_MANAGE_STORAGE: true

SAS API Access

V4_CFG_SAS_API_KEY: 'XXX' V4_CFG_SAS_API_SECRET: 'XXX' V4_CFG_ORDER_NUMBER: 'XXXX'

CR Access

V4_CFG_CR_USER:

V4_CFG_CR_PASSWORD:

Ingress

V4_CFG_INGRESS_TYPE: ingress

V4_CFG_INGRESS_FQDN:

V4_CFG_INGRESS_FQDN: viya4_frg.ingress.endpoint V4_CFG_TLS_MODE: "full-stack" # [full-stack|front-door|disabled]

Postgres

V4_CFG_POSTGRES_TYPE: external #[internal|external]

LDAP

V4_CFG_EMBEDDED_LDAP_ENABLE: true

Consul UI

V4_CFG_CONSUL_ENABLE_LOADBALANCER: false

SAS/CONNECT

V4_CFG_CONNECT_ENABLE_LOADBALANCER: false

VIYA ORDER - Henry - We can leave this alone and ansible will download if left blank

Or we can fill in since we already downloaded deployment assets

V4_CFG_ORDER_NUMBER:

V4_CFG_CADENCE_NAME:

V4_CFG_CADENCE_VERSION:

Monitoring and Logging

uncomment and update the below values when deploying the viya4-monitoring-kubernetes stack

V4M_BASE_DOMAIN:

henmo09 commented 3 years ago

here is an output root@henmo:~/project/viya4-deployment/roles/baseline/defaults# kubectl get pods -n viya4-frg-v1 |grep sas-workflow-manager-app sas-workflow-manager-app-6bbd577b57-ccrxq 0/1 Init:CrashLoopBackOff 74 5h54m root@henmo:~/project/viya4-deployment/roles/baseline/defaults# kubectl describe pods -n viya4-frg-v1 |grep sas-workflow-manager-app Name: sas-workflow-manager-app-6bbd577b57-ccrxq Labels: app=sas-workflow-manager-app app.kubernetes.io/name=sas-workflow-manager-app sas.com/component-name: sas-workflow-manager-app Controlled By: ReplicaSet/sas-workflow-manager-app-6bbd577b57 KUBE_POD_NAME: sas-workflow-manager-app-6bbd577b57-ccrxq (v1:metadata.name) sas-workflow-manager-app: Image: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-workflow-manager-app:2.9.0-20200929.1601422577467 Liveness: exec [/opt/sas/viya/home/bin/sas-liveness-tool -manifest-file /opt/sas/viya/home/share/sas-workflow-manager-app/run-manifest.json] delay=0s timeout=1s period=10s #success=1 #failure=3 SAS_K8S_DEPLOYMENT_NAME: sas-workflow-manager-app root@henmo:~/project/viya4-deployment/roles/baseline/defaults# kubectl get pods -n viya4-frg-v1 |grep sas-workflow-manager-app sas-workflow-manager-app-6bbd577b57-ccrxq 0/1 Init:CrashLoopBackOff 74 5h54m root@henmo:~/project/viya4-deployment/roles/baseline/defaults#

henmo09 commented 3 years ago

s

henmo09 commented 3 years ago

/project/viya4-deployment/roles/baseline/defaults# kubectl get pods -n viya4-frg-v1 |grep sas-workflow-manager-app sas-workflow-manager-app-6bbd577b57-ccrxq 0/1 Init:CrashLoopBackOff 74 5h54m

thpang commented 3 years ago

Have you looked at the logs of the pods to see why they have not started? I would start with consul, then look at the cache pods, then logon. Good places to start.

henmo09 commented 3 years ago

these are one of the logs, but not much info. 4-frg-v1 sas-workflow-manager-app-6bbd577b57-ccrxq 0/1 Init:CrashLoopBackOff 231 19h root@henmo:~# kubectl logs sas-analytics-components-65cf89944f-s7fb6 -n viya4-frg-v1 Error from server (BadRequest): container "sas-analytics-components" in pod "sas-analytics-components-65cf89944f-s7fb6" is waiting to start: PodInitializing root@henmo:~# kubectl logs sas-analytics-events-5575d8c5cc-g7nsl -n viya4-frg-v1 Error from server (BadRequest): container "sas-analytics-events" in pod "sas-analytics-events-5575d8c5cc-g7nsl" is waiting to start: PodInitializing root@henmo:~# kubectl logs sas-backup-purge-job-1628727300-65st8 -n viya4-frg-v1 error: a container name must be specified for pod sas-backup-purge-job-1628727300-65st8, choose one of: [sas-backup-purge-job sas-backup-agent] or one of the init containers: [sas-certframe] root@henmo:~#

henmo09 commented 3 years ago

see logs for logon and pod describe.

root@henmo:~# kubectl logs sas-logon-app-764795d975-vf7ws -n viya4-frg-v1 Error from server (BadRequest): container "sas-logon-app" in pod "sas-logon-app-764795d975-vf7ws" is waiting to start: PodInitializing root@henmo:~# kubectl describe pod sas-logon-app-764795d975-vf7ws -n viya4-frg-v1 Name: sas-logon-app-764795d975-vf7ws Namespace: viya4-frg-v1 Priority: 0 Node: aks-stateless-38049675-vmss000000/192.168.0.5 Start Time: Wed, 11 Aug 2021 18:47:06 +0000 Labels: app=sas-logon-app app.kubernetes.io/name=sas-logon-app pod-template-hash=764795d975 sas.com/deployment=sas-viya workload.sas.com/class=stateless Annotations: prometheus.io/path: /internal/metrics prometheus.io/port: 10445 prometheus.io/scheme: https prometheus.io/scrape: true sas.com/certificate-file-format: jks sas.com/component-name: sas-logon-app sas.com/component-version: 2.39.9-20201002.1601645502383 sas.com/kustomize-base: spring sas.com/pod-uses-readiness-probe: http sas.com/tls-enabled-ports: all sas.com/version: 2.39.9 sidecar.istio.io/proxyCPU: 15m sidecar.istio.io/proxyMemory: 115Mi Status: Pending IP: 10.244.2.178 IPs: IP: 10.244.2.178 Controlled By: ReplicaSet/sas-logon-app-764795d975 Init Containers: sas-certframe: Container ID: containerd://72b7afc28d8d20212a463c58b36afb0987db0173ae4b416fe93ac7695fccf4a5 Image: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.7.2-20201208.1607438373197 Image ID: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe@sha256:2ce3072fb2693e8b89301a2bc314dcc68fc1c8fa92901e3568202df9ef995030 Port: Host Port: State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Thu, 12 Aug 2021 14:14:00 +0000 Finished: Thu, 12 Aug 2021 14:14:00 +0000 Ready: False Restart Count: 233 Limits: cpu: 500m memory: 500Mi Requests: cpu: 50m memory: 50Mi Environment Variables from: sas-certframe-ingress-certificate-config-cmm2t44t88 ConfigMap Optional: false sas-certframe-user-config-kfckf2c4g8 ConfigMap Optional: false sas-certframe-java-config-gf4kt94898 ConfigMap Optional: false Environment: KUBE_POD_NAME: sas-logon-app-764795d975-vf7ws (v1:metadata.name) SAS_CERTFRAME_TOKEN_DIR: /certframe-token SAS_ADDITIONAL_CA_CERTIFICATES_DIR: /customer-provided-ca-certificates Mounts: /certframe-token from certframe-token (rw) /customer-provided-ca-certificates from customer-provided-ca-certificates (rw) /security from security (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-49tpb (ro) Containers: sas-logon-app: Container ID: Image: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-logon-app:2.39.9-20201002.1601645502383 Image ID: Ports: 8080/TCP, 10445/TCP Host Ports: 0/TCP, 0/TCP State: Waiting Reason: PodInitializing Ready: False Restart Count: 0 Limits: cpu: 2 memory: 1Gi Requests: cpu: 50m memory: 763Mi Readiness: http-get https://:http-internal/internal/ready delay=0s timeout=1s period=10s #success=1 #failure=3 Environment Variables from: sas-java-config-t7t5thbgkd ConfigMap Optional: false sas-shared-config-5m2f4bdg2c ConfigMap Optional: false sas-consul-client Secret Optional: false sas-spring-management-config-d64bbkhb97 ConfigMap Optional: false sas-java-tls-config-fch4777298 ConfigMap Optional: false Environment: SAS_K8S_DEPLOYMENT_NAME: sas-logon-app Mounts: /opt/sas/viya/config/etc/SASSecurityCertificateFramework/cacerts from security (rw,path="cacerts") /opt/sas/viya/config/etc/SASSecurityCertificateFramework/private from security (rw,path="private") /opt/sas/viya/config/tmp from tmp (rw) /security from security (rw) /tmp from tmp (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-49tpb (ro) Conditions: Type Status Initialized False Ready False ContainersReady False PodScheduled True Volumes: certframe-token: Type: Secret (a volume populated by a Secret) SecretName: sas-certframe-token Optional: false security: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: customer-provided-ca-certificates: Type: ConfigMap (a volume populated by a ConfigMap) Name: sas-customer-provided-ca-certificates-29kdmk686c Optional: false tmp: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: default-token-49tpb: Type: Secret (a volume populated by a Secret) SecretName: default-token-49tpb Optional: false QoS Class: Burstable Node-Selectors: Tolerations: node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s workload.sas.com/class=stateful:NoSchedule workload.sas.com/class=stateless:NoSchedule Events: Type Reason Age From Message

Normal Pulled 43m (x222 over 19h) kubelet Container image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.7.2-20201208.1607438373197" already present on machine Warning BackOff 3m31s (x5327 over 19h) kubelet Back-off restarting failed container

thpang commented 3 years ago

At this point you'll have to figure out the best way for you to debug your environment. If the deployment ran without failure, there is more than likely a configuration issue you need to investigate. As I stated above, looking at the logs for your pods is going to be key. If you need a tool to help, use Lens. It's a great UI for helping one navigate their kubernetes cluster. If you have some specific information about the deployment you feel is causing the issue, open another issue with information there about the problem.