Skip to main content

Browse the archive

Revision 4c8c03db7a77415208793b2fec3509fe6ca3b31c authored by Tom Hadlaw on 18 June 2024, 21:54:34 UTC, committed by Tom on 21 June 2024, 06:31:26 UTC 
k8s: improve user facing error logging for k8s decode errors.
 
Errors such as "invalid character 'T' looking for beginning of value"
can be emitted by k8s client-go libraries if there is a problem decoding
the underlying k8s object from the apiserver.

Specifically, this can occur if apiserver is sending a json containing
an error message and not a k8s object.

These errors can be confusing, so this adds a k8s error handler case to
catch these and emit a more user friendly message.

Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
1 parent 3fc57b3
Raw File
.clomonitor.yml 
# CLOMonitor metadata file

exemptions:
  - check: slack_presence
    reason: "The Cilium slack community can be found at http://slack.cilium.io/" # Justification of this exemption

  - check: dangerous_workflow
    reason: >
      "It is safe to run code checkout '${{ github.event.pull_request.head.sha }}' 
      and 'github.event.pull_request.head.ref' in .github/workflows/build-images-base.yaml 
      as this workflow is only permitted to be executed after an explicit approval of a 
      subset of committers."

  - check: signed_releases
    reason: >
      "All Cilium release images are cryptographically signed during build by cosign. 
      Images are hosted in Quay. OpenSSF Scorecard check is currently limited to repositories 
      hosted on GitHub, and does not support other source hosting repositories."

  - check: token_permissions
    reason: >
      "Reason to use every non-read-only token in GitHub workflows is commented in the respective workflow files."
back to top