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

Imported service not respective topology awareness hints #263

Open
techmouse84 opened this issue Jan 27, 2023 · 1 comment
Open

Imported service not respective topology awareness hints #263

techmouse84 opened this issue Jan 27, 2023 · 1 comment
Milestone

Comments

@techmouse84
Copy link

Tested in EKS 1.24

Verified with the following setup .
curling the imported service from an ubuntu pod will show that it's randomly distributed across the 2 pods.
Expects imported service to respect topology awareness and hits only 1 pod.

apiVersion: apps/v1
kind: Deployment
metadata:
  namespace: monitoring
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - name: nginx
          image: nginx:1.14.2
          ports:
            - containerPort: 80
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - nginx
            topologyKey: failure-domain.beta.kubernetes.io/zone

---

kind: Service
apiVersion: v1
metadata:
  namespace: monitoring
  name: nginx-service
  annotations:
    service.kubernetes.io/topology-aware-hints: Auto
spec:
  selector:
    app: nginx
  ports:
    - port: 80
@runakash
Copy link
Member

Hello techmouse84 - We do not support Topology Aware Hints yet. Even mcs spec references the deprecated Topology API. We can definitely have a look into integrating in future milestones.

@runakash runakash added this to the 0.4.0 milestone Jan 27, 2023
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

No branches or pull requests

2 participants