pulp / pulp/pulp-operator

APIRoot path wrong formatted - has a new line after /pulp/

Open
#1,456 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue Triage-Needed
Dominant language
Go
Stars
88
Forks
66
Avg merge
53m
Merged PRs (30d)
1

Description

Version
1.0.0 and 1.0.1

Describe the bug
API enters in crashloop after deployment, pulp config looks like below

is_nginx_ingress: true
web:
    replicas: 0

To Reproduce
API Deployment looks like below after is deployed by the operator.

          livenessProbe:
            failureThreshold: 10
            httpGet:
              path: |-
                /pulp/
                api/v3/status/
              port: 24817
              scheme: HTTP
            initialDelaySeconds: 3
            periodSeconds: 20
            successThreshold: 1
            timeoutSeconds: 10
          name: api
          ports:
            - containerPort: 24817
              protocol: TCP
          readinessProbe:
            exec:
              command:
                - /usr/bin/readyz.py
                - |-
                  /pulp/
                  api/v3/status/
            failureThreshold: 1
            initialDelaySeconds: 3
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10

Ingress path looks like below after is deployed by the operator.

          - backend:
              service:
                name: pulp-api-svc
                port:
                  name: api-24817
            path: |-
              /pulp/
              api/v3/

API pod crashloop error

"GET /pulp/%0Aapi/v3/status/ HTTP/1.1" 404 9370

Expected behavior
Path should not have a new line, should look like below.

path:  /pulp/api/v3/

Additional context

Contributor guide

Open the contributing guide

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.

Research direction

Start by tracing how the operator generates the API liveness probe, readiness command, and Ingress path shown in the deployment output. Compare the configured /pulp/ prefix with the generated paths; done means the manifests use /pulp/api/v3/status/ and /pulp/api/v3/ without an embedded newline, preventing the API pod crashloop.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.