rtoya / memo Goto Github PK

0 test/sample-cronjob()
- Error: CronJob sample-cronjob is suspended
Error: CronJob sample-cronjob is suspended.
Solution:
1. Check the reason for suspension using kubectl describe cronjob sample-cronjob.
2. Resolve any issues mentioned in the description.
3. Resume the CronJob by running kubectl rollout restart cronjob/sample-cronjob.

1 argocd/argocd-application-controller(argocd-application-controller)
- Error: StatefulSet uses the service argocd/argocd-application-controller which does not exist.
Error: StatefulSet uses a service that does not exist.
Solution:
1. Check if the service argocd/argocd-application-controller has been created.
2. If not, create the service using kubectl create service command.
3. Update the StatefulSet to use the correct service name.

2 admin-dev/lab()
- Error: Deployment admin-dev/lab has 1 replicas but 2 are available
Error: Deployment admin-dev/lab has 1 replicas but 2 are available.
Solution:
1. Check the deployment configuration using kubectl get deployment admin-dev/lab.
2. Update the replicas to the desired number using kubectl scale deployment admin-dev/lab --replicas=1.
3. Verify the changes with kubectl get deployment admin-dev/lab.

3 backend-dev/mono-backend-engagement()
- Error: Deployment backend-dev/mono-backend-engagement has 1 replicas but 2 are available
Error: The deployment backend-dev/mono-backend-engagement has 1 replica configured, but only 2 replicas are available.

Solution:
1. Update the deployment configuration to have 2 replicas.
2. Run kubectl apply -f deployment.yaml to apply the new configuration.
3. Monitor the deployment to ensure both replicas are running successfully.

4 analysis-dev/text-classification-bert-server(text-classification-bert-server)
- Error: Service has no endpoints, expected label app=text-classification-bert-server
- Error: Service has no endpoints, expected label cluster=wevox
- Error: Service has no endpoints, expected label env=dev
Error: Service has no endpoints due to missing labels app=text-classification-bert-server, cluster=wevox, env=dev.
Solution: 1. Add labels app=text-classification-bert-server, cluster=wevox, env=dev to the service. 2. Ensure pods with matching labels are running.

5 backend-dev/api-admin(api-admin)
- Error: Service has not ready endpoints, pods: [Pod/api-admin-679bdc7967-5zc2m], expected 1
Error: Service has not ready endpoints, pods: [Pod/api-admin-679bdc7967-5zc2m], expected 1.
Solution: 1. Check the status of the pod named api-admin-679bdc7967-5zc2m. 2. Ensure the pod is running and ready. 3. Restart the pod if necessary.

6 backend-dev/custom-reports(custom-reports)
- Error: Service has no endpoints, expected label app=custom-reports
- Error: Service has no endpoints, expected label cluster=wevox
- Error: Service has no endpoints, expected label env=dev
Error: Service has no endpoints due to missing labels (app=custom-reports, cluster=wevox, env=dev).
Solution:
1. Add labels to the service using kubectl annotate service <service-name> app=custom-reports cluster=wevox env=dev.
2. Ensure pods have matching labels.
3. Check if the pods are healthy and running.

7 backend-dev/gateway(gateway)
- Error: Service has not ready endpoints, pods: [Pod/gateway-6df5bb4dbf-blp24], expected 1
Error: Service has no ready endpoints, pods: [Pod/gateway-6df5bb4dbf-blp24], expected 1.
Solution:
1. Check if the pod gateway-6df5bb4dbf-blp24 is running and healthy.
2. Verify if the pod is correctly labeled and selected by the service.
3. Ensure the pod has the correct port exposed and ready.

8 backend-dev/mono-backend-engagement(mono-backend-engagement)
- Error: Service has not ready endpoints, pods: [Pod/mono-backend-engagement-b4f9d6d7-r6hgx], expected 1
Error: Service has no ready endpoints, pods: [Pod/mono-backend-engagement-b4f9d6d7-r6hgx], expected 1.
Solution: 1. Check if pod is running and healthy. 2. Ensure correct labels and selectors are used. 3. Verify network policies and firewall rules.

9 test/deploy-test-77d7f4fdb7-mwbq6(deploy-test-77d7f4fdb7-mwbq6)
- Error: Service has no endpoints, expected label app=pod-example
- Error: Service has no endpoints, expected label pod-template-hash=77d7f4fdb7
Error: Service has no endpoints, missing labels app=pod-example and pod-template-hash=77d7f4fdb7.
Solution:
1. Add labels app=pod-example and pod-template-hash=77d7f4fdb7 to the service configuration.
2. Ensure that the labels match the selectors in the pods.
3. Restart the service to apply the changes.

10 admin-dev/lab(lab)
- Error: Service has not ready endpoints, pods: [Pod/lab-56fc49cd69-8fnjp Pod/lab-6c989d8b7-mslvp], expected 2
Error: Service has no ready endpoints for pods: [Pod/lab-56fc49cd69-8fnjp Pod/lab-6c989d8b7-mslvp], expected 2.
Solution: 1. Check if pods are running and healthy. 2. Ensure correct labels and selectors are set. 3. Verify network policies and firewall rules.

11 default/akki-test-gwszw(akki-test-gwszw)
- Error: Back-off pulling image "649093048886.dkr.ecr.ap-northeast-1.amazonaws.com/release/wevox-engagement:5136cf3"
Error: Back-off pulling image "649093048886.dkr.ecr.ap-northeast-1.amazonaws.com/release/wevox-engagement:5136cf3"

Solution:
1. Check the image repository for availability.
2. Ensure correct image name and tag.
3. Verify network connectivity to the repository.
5. Restart the deployment or pod.

12 admin-dev/lab-56fc49cd69-8fnjp(Deployment/lab)
- Error: secret "lab" not found
Error: secret "lab" not found

Solution:
1. Check if the secret "lab" exists in the Kubernetes cluster.
2. If not, create the secret using the 'kubectl create secret' command.
3. Verify the secret was created successfully by running 'kubectl get secret lab'.

13 admin-dev/lab-6c989d8b7-mslvp(Deployment/lab)
- Error: secret "lab" not found
Error: secret "lab" not found

Solution:
1. Check if the secret "lab" exists in the Kubernetes cluster.
2. If not, create the secret using the 'kubectl create secret' command.
3. Verify the secret was created successfully by running 'kubectl get secret lab'.

14 backend-dev/api-admin-679bdc7967-5zc2m(Deployment/api-admin)
- Error: back-off 5m0s restarting failed container=api-admin pod=api-admin-679bdc7967-5zc2m_backend-dev(e045088a-b374-4767-8895-3e63a46f857c)
- Error: the last termination reason is Error container=api-admin pod=api-admin-679bdc7967-5zc2m
Error: Container "api-admin" in pod "api-admin-679bdc7967-5zc2m_backend-dev" failed to restart due to an error.

Solution:
1. Check the logs of the container "api-admin" for more details on the error.
2. Fix the issue causing the error in the container.
3. Restart the pod to apply the changes.

15 backend-dev/gateway-6df5bb4dbf-blp24(Deployment/gateway)
- Error: back-off 5m0s restarting failed container=gateway pod=gateway-6df5bb4dbf-blp24_backend-dev(edb23c78-73ce-4049-8a5d-3c66849ba06d)
- Error: the last termination reason is Error container=gateway pod=gateway-6df5bb4dbf-blp24
Error: Container named 'gateway' in pod 'gateway-6df5bb4dbf-blp24_backend-dev' failed to start and is continuously restarting.
Solution:
1. Check the logs of the container to identify the specific error causing the failure.
2. Make necessary changes to the container configuration or code to resolve the issue.
3. Restart the pod to apply the changes and ensure the container starts successfully.

16 backend-dev/mono-backend-engagement-b4f9d6d7-r6hgx(Deployment/mono-backend-engagement)
- Error: back-off 5m0s restarting failed container=mono-backend-engagement pod=mono-backend-engagement-b4f9d6d7-r6hgx_backend-dev(ea619f8b-bc08-4394-9744-00a8b29efaa4)
- Error: the last termination reason is Error container=mono-backend-engagement pod=mono-backend-engagement-b4f9d6d7-r6hgx
Error: Container "mono-backend-engagement" in pod "mono-backend-engagement-b4f9d6d7-r6hgx_backend-dev" failed to start and is in a back-off state.
Solution:
1. Check the logs of the container to identify the specific error.
2. Fix the issue causing the container to fail.
3. Restart the pod to apply the changes.

17 front-dev/wevox-front2(wevox-front2)
- Error: Ingress uses the service front-dev/cs-workflow-web which does not exist.
- Error: Ingress uses the service front-dev/roppongi-workflow-web which does not exist.
- Error: Ingress uses the service front-dev/roppongi-yaccount-web which does not exist.
- Error: Ingress uses the service front-dev/roppongi-authentication-web which does not exist.
Error: Ingress is referencing services that do not exist.

Solution:
1. Check the spelling and naming of the services mentioned in the error message.
2. Create the missing services front-dev/cs-workflow-web, front-dev/roppongi-workflow-web, front-dev/roppongi-yaccount-web, front-dev/roppongi-authentication-web.

18 admin-dev/wevox-admin(wevox-admin)
- Error: Ingress uses the service admin-dev/ssl-redirect which does not exist.
- Error: Ingress uses the service admin-dev/apply-web which does not exist.
- Error: Ingress uses the service admin-dev/ssl-redirect which does not exist.
- Error: Ingress uses the service admin-dev/ssl-redirect which does not exist.
- Error: Ingress uses the service admin-dev/apply-web which does not exist.
Error: The Ingress is using services that do not exist.

Solution:
1. Check the spelling and existence of the services admin-dev/ssl-redirect and admin-dev/apply-web.
2. Create the missing services if they do not exist in the cluster.

19 front-dev/wevox-front(wevox-front)
- Error: Ingress uses the service front-dev/ssl-redirect which does not exist.
- Error: Ingress uses the service front-dev/ebisu-workflow-web which does not exist.
- Error: Ingress uses the service front-dev/ssl-redirect which does not exist.
Error: Ingress is referencing services that do not exist.

Solution:
1. Create the services front-dev/ssl-redirect and front-dev/ebisu-workflow-web.
2. Ensure that the services are running and accessible.
5. Update the Ingress configuration to point to the correct services.