ServiceDefinition vshn.appcat.vshn.io/v1/VSHNForgejo fails to create #43

New issue

Closed

opened 2025-04-09 06:16:48 +00:00 by tobru · 0 comments

tobru commented

2025-04-09 06:16:48 +00:00

Owner

Description

The Service Definition for vshn.appcat.vshn.io/v1/VSHNForgejo fails to create an instance.

Actual Behavior

Creating an instance for this service definition leads into:

Kubernetes API error: (404) Reason: Not Found HTTP response headers: HTTPHeaderDict({'Audit-Id': '970c7642-0a4b-4749-b48e-afac09714b2c, 971f34a4-80f8-45b0-8b46-459a8176c9bb', 'Cache-Control': 'no-cache, private, no-cache, private', 'Content-Length': '19', 'Content-Type': 'text/plain; charset=utf-8', 'Date': 'Wed, 09 Apr 2025 06:12:41 GMT', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '0425ba2b-aed3-442b-ad78-064f8f6331ac', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'bd0d6b0d-a1a2-4317-a350-bb4e00e07917'}) HTTP response body: 404 page not found

Manually creating a VSHNForgejo resource on the control-plane works:

apiVersion: vshn.appcat.vshn.io/v1
kind: VSHNForgejo
metadata:
  name: myforgejo
spec:
  parameters:
    service:
      adminEmail: "demo@example.com"
      fqdn:
        - "mygit.example.com"
    security:
      deletionProtection: true
  writeConnectionSecretToRef:
    name: myforgejo-creds

## Description The Service Definition for `vshn.appcat.vshn.io/v1/VSHNForgejo` fails to create an instance. ## Actual Behavior Creating an instance for this service definition leads into: ``` Kubernetes API error: (404) Reason: Not Found HTTP response headers: HTTPHeaderDict({'Audit-Id': '970c7642-0a4b-4749-b48e-afac09714b2c, 971f34a4-80f8-45b0-8b46-459a8176c9bb', 'Cache-Control': 'no-cache, private, no-cache, private', 'Content-Length': '19', 'Content-Type': 'text/plain; charset=utf-8', 'Date': 'Wed, 09 Apr 2025 06:12:41 GMT', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '0425ba2b-aed3-442b-ad78-064f8f6331ac', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'bd0d6b0d-a1a2-4317-a350-bb4e00e07917'}) HTTP response body: 404 page not found ``` Manually creating a `VSHNForgejo` resource on the control-plane works: ``` apiVersion: vshn.appcat.vshn.io/v1 kind: VSHNForgejo metadata: name: myforgejo spec: parameters: service: adminEmail: "demo@example.com" fqdn: - "mygit.example.com" security: deletionProtection: true writeConnectionSecretToRef: name: myforgejo-creds ```