Service don't have clusterIP, and lowable-workflow-ui is not accessable

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes

Research direction

Start by rendering the Flowable Helm chart with the posted host, ingress, and PostgreSQL values, then compare the generated UI Service and Ingress with the manifests shown in the issue. Trace how the UI Service selector, service type, and ingress hostname are configured. Done means the rendered configuration routes workflow.mydomain.xxx to the UI successfully.

Written by the indexing model from the issue text.

Description

This is what I modified to my value

host:
  external: workflow.mydomain.xxx
ingress:
  class: "nginx"
  useHost: true
postgres:
  storage:
    storageClassName: "microk8s-hostpath-retain"

It successfully installed, but I found flowable-workflow-flowable-ui service's clusterIP is None:

kind: Service
apiVersion: v1
metadata:
  name: flowable-workflow-flowable-ui
  namespace: workflow
  uid: 60c3abd3-4284-42bb-add8-42b7be8426d4
  resourceVersion: '3731938'
  creationTimestamp: '2023-11-27T09:56:39Z'
  labels:
    app.kubernetes.io/instance: flowable-workflow
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ui
    helm.sh/chart: flowable-6.8.0
  annotations:
    meta.helm.sh/release-name: flowable-workflow
    meta.helm.sh/release-namespace: workflow
  managedFields:
    - manager: kubeapps-apis
      operation: Update
      apiVersion: v1
      time: '2023-11-27T09:56:39Z'
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:meta.helm.sh/release-name: {}
            f:meta.helm.sh/release-namespace: {}
          f:labels:
            .: {}
            f:app.kubernetes.io/instance: {}
            f:app.kubernetes.io/managed-by: {}
            f:app.kubernetes.io/name: {}
            f:helm.sh/chart: {}
        f:spec:
          f:clusterIP: {}
          f:internalTrafficPolicy: {}
          f:ports:
            .: {}
            k:{"port":8080,"protocol":"TCP"}:
              .: {}
              f:name: {}
              f:port: {}
              f:protocol: {}
              f:targetPort: {}
          f:selector: {}
          f:sessionAffinity: {}
          f:type: {}
spec:
  ports:
    - name: http
      protocol: TCP
      port: 8080
      targetPort: 8080
  selector:
    app.kubernetes.io/instance: flowable-workflow
    app.kubernetes.io/name: flowable-workflow-ui
  clusterIP: None
  clusterIPs:
    - None
  type: ClusterIP
  sessionAffinity: None
  ipFamilies:
    - IPv4
  ipFamilyPolicy: SingleStack
  internalTrafficPolicy: Cluster
status:
  loadBalancer: {}

And I can't access it from https://workflow.mydomain.xxx , why?

Dominant language
Mustache
Stars
5
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flowable/helm

All issues in flowable/helm

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.