You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
I have created a load balancer service with cloud provider as aws. The classic load balancer was also created in AWS however, the service shows the external I as still pending. And my pod is not able to identify the AWS RDS database hostname. Am I missing something ? Appreciate your help please. Thank you a ton.
Below is my LB service
apiVersion: v1
kind: Service
metadata:
name: cust-db-mgmt-loadbalance-service
namespace: sai
spec:
type: LoadBalancer
selector:
app: cust-db-mgmt
ports:
port: 8080
targetPort: 8080
nodePort: 30002
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution. Note that acs-engine is deprecated--see https://github.com/Azure/aks-engine instead.
I have created a load balancer service with cloud provider as aws. The classic load balancer was also created in AWS however, the service shows the external I as still pending. And my pod is not able to identify the AWS RDS database hostname. Am I missing something ? Appreciate your help please. Thank you a ton.
Below is my LB service
apiVersion: v1
kind: Service
metadata:
name: cust-db-mgmt-loadbalance-service
namespace: sai
spec:
type: LoadBalancer
selector:
app: cust-db-mgmt
ports:
targetPort: 8080
nodePort: 30002
The text was updated successfully, but these errors were encountered: