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

Issue with port 8081 #24

Open
bharath-muthineni opened this issue Sep 24, 2024 · 1 comment
Open

Issue with port 8081 #24

bharath-muthineni opened this issue Sep 24, 2024 · 1 comment

Comments

@bharath-muthineni
Copy link

Hi,
I'm trying to run Vepsa with these helm charts. After the pod is up and running, I tried port-forwarding 19071 and 8081 ports to my machine.
19071 gives a success response, however, 8081 gives connection refused error. I tried execing into the pod and ran curl localhost:8081, the error is the same.
Is there anything wrong with my kubernetes cluster?
Here is my pod manifest:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apps/v1","kind":"StatefulSet","metadata":{"annotations":{},"labels":{"app":"vespa"},"name":"vespa","namespace":"xplus-apps"},"spec":{"replicas":1,"selector":{"matchLabels":{"app":"vespa"}},"serviceName":"vespa","template":{"metadata":{"labels":{"app":"vespa"}},"spec":{"containers":[{"image":"vespaengine/vespa:8.277.17","imagePullPolicy":"IfNotPresent","name":"vespa","ports":[{"containerPort":19071},{"containerPort":8081}],"readinessProbe":{"httpGet":{"path":"/state/v1/health","port":19071,"scheme":"HTTP"}},"securityContext":{"privileged":true,"runAsUser":0},"volumeMounts":[{"mountPath":"/opt/vespa/var/","name":"vespa-storage"}]}],"nodeSelector":{"bots":"true"}}},"volumeClaimTemplates":[{"metadata":{"name":"vespa-storage"},"spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"5Gi"}}}}]}}
  creationTimestamp: "2024-09-24T07:30:23Z"
  generation: 1
  labels:
    app: vespa
  name: vespa
  namespace: apps
  resourceVersion: "2565895621"
  uid: 8e9580ae-5bf9-4b32-ac06-1342b71cd5ab
spec:
  persistentVolumeClaimRetentionPolicy:
    whenDeleted: Retain
    whenScaled: Retain
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: vespa
  serviceName: vespa
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: vespa
    spec:
      containers:
      - image: vespaengine/vespa:8.277.17
        imagePullPolicy: IfNotPresent
        name: vespa
        ports:
        - containerPort: 19071
          protocol: TCP
        - containerPort: 8081
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /state/v1/health
            port: 19071
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources: {}
        securityContext:
          privileged: true
          runAsUser: 0
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /opt/vespa/var/
          name: vespa-storage
      dnsPolicy: ClusterFirst
      nodeSelector:
        bots: "true"
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
  updateStrategy:
    rollingUpdate:
      partition: 0
    type: RollingUpdate
  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: vespa-storage
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 5Gi
      volumeMode: Filesystem
    status:
      phase: Pending

Please help me resolving this.

@bharath-muthineni
Copy link
Author

I have increased the memory limit from 2G to 3G and the process which runs on port 8081 has started up.
In case, this is the only issue then please mark it as done and close.
Thank you!!

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

1 participant