Skip to content

Unknown format "int32" ignored in schema at path #257

Open
@phspies

Description

@phspies

Trying to use this module to validate some Kubernetes YAML files against the K8's Spec file and it seems to think int32, int64, etc is not valid. Seems the K8's spec file uses a lot of these "unknown" formats, so is this module out of date or is the K8's spec file wrong?

unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/ports/items/properties/hostPort"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/failureThreshold"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/grpc/properties/port"
unknown format "int-or-string" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/httpGet/properties/port"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/initialDelaySeconds"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/periodSeconds"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/successThreshold"
unknown format "int-or-string" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/tcpSocket/properties/port"
unknown format "int64" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/terminationGracePeriodSeconds"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/readinessProbe/properties/timeoutSeconds"
unknown format "int64" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/securityContext/properties/runAsGroup"
unknown format "int64" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/securityContext/properties/runAsUser"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/startupProbe/properties/failureThreshold"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/startupProbe/properties/grpc/properties/port"
unknown format "int-or-string" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/startupProbe/properties/httpGet/properties/port"
unknown format "int32" ignored in schema at path "#/properties/spec/properties/ephemeralContainers/items/properties/startupProbe/properties/initialDelaySeconds"

So the K8's configuration file has this spec in it that is flagged by this module:
"properties": { "containerPort": { "description": "Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.", "format": "int32", "type": "integer"

From the Swagger spec it seems these value are correct: https://swagger.io/specification/v2/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions