Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing port number might bring downtime in custom-metrics-stackdriver-adapter #721

Closed
CatherineF-dev opened this issue May 7, 2024 · 3 comments · Fixed by #722
Closed

Comments

@CatherineF-dev
Copy link
Contributor

CatherineF-dev commented May 7, 2024

Previously, custom-metrics-stackdriver-adapter is using targetPort 443.

After adding readiness probe, targetPort is changed to 6443

#710

@kuanhn
Copy link

kuanhn commented May 8, 2024

@CatherineF-dev
Do you have any updates related to this issue?
Our HPA was down today after the cluster was updated to 1.27.
The version of custom-metric being used is 0.14.2

@CatherineF-dev
Copy link
Contributor Author

Could you share your service yaml? Is targetPort using 6443 or 443

apiVersion: v1
kind: Service
metadata:
  labels:
    run: custom-metrics-stackdriver-adapter
    k8s-app: custom-metrics-stackdriver-adapter
    kubernetes.io/cluster-service: 'true'
    kubernetes.io/name: Adapter
  name: custom-metrics-stackdriver-adapter
  namespace: custom-metrics
spec:
  ports:
  - port: 443
    protocol: TCP
    targetPort: 6443
  selector:
    run: custom-metrics-stackdriver-adapter
    k8s-app: custom-metrics-stackdriver-adapter
  type: ClusterIP

@CatherineF-dev
Copy link
Contributor Author

@kuanhn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants