reopen - Missing required Service.spec.ports in Kubernetes #2655
Comments
6543
pushed a commit
that referenced
this issue
Nov 2, 2023
Closes #2655. [Pipeline](https://woodpecker-ci.org/docs/next/usage/services#complete-pipeline-example): ```yaml services: database: image: mysql environment: - MYSQL_DATABASE=test - MYSQL_ROOT_PASSWORD=example ports: - 3306 steps: get-version: image: ubuntu commands: - ( apt update && apt dist-upgrade -y && apt install -y mysql-client 2>&1 )> /dev/null - sleep 60s # need to wait for mysql-server init - echo 'SHOW VARIABLES LIKE "version"' | mysql -uroot -hdatabase test -pexample ``` Service: ```yaml apiVersion: v1 kind: Service metadata: name: wp-01hdq6gbkw1mn6k1655fs3rntf-0-services-0 namespace: woodpecker-runtime ... selfLink: >- /api/v1/namespaces/woodpecker-runtime/services/wp-01hdq6gbkw1mn6k1655fs3rntf-0-services-0 status: loadBalancer: {} spec: ports: - protocol: TCP port: 3306 targetPort: 3306 selector: step: database clusterIP: 10.43.180.120 clusterIPs: - 10.43.180.120 type: ClusterIP sessionAffinity: None ipFamilies: - IPv4 ipFamilyPolicy: SingleStack internalTrafficPolicy: Cluster ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally posted by @J-Ha in #1238 (comment)
this problem still exists.
this problem has nothing todo with the helm-chart.
it is more about the kubernetes backend and the service that should be created by a job
the service of the job awaits a port:
https://github.com/woodpecker-ci/woodpecker/blob/next-release/1.0.3/pipeline/backend/kubernetes/service.go#L26
but there is no option to pass a service port into this by the
.woodpecker.ymland the job terminates on creation with the error of:
is invalid: spec.ports: Required valuethere is something within the schema.json defined, nothing in the documentation. But even when setting a port in the array im getting the same error.
https://github.com/woodpecker-ci/woodpecker/blob/v1.0.3/pipeline/schema/schema.json#L580
The text was updated successfully, but these errors were encountered: