Python: Dictionary representations of k8s resource model objects are not valid k8s resource manifest representations

Created on 14 Nov 2017 · 6Comments · Source: kubernetes-client/python

My use case is that I'd like to build up a representation of various Kubernetes resources via the classes in kubernetes.client.models and then generate the manifest yaml files for these resources via printing to YAML files the to_dictrepresentations of these resource objects. However, because all the attributes are snake cased, the end YAML also has snake cased keys (which are not valid k8s manifest keys and fail validation).

Example:

with open('deployment.yaml, 'w') as outfile:
    yaml.dump(deploymemnt_resource.to_dict(), outfile, default_flow_style=False)

Resulting deployment.yaml file:

api_version: extensions/v1beta1
kind: Deployment
metadata:
  name: testing
spec:
  progress_deadline_seconds: 300
  replicas: 1
  template:
    metadata:
      labels:
        app: testing
    spec:
      containers:
      - name: testing
        readiness_probe:
          http_get:
            path: /_meta/0/info
            port: http

The progress_deadline_seconds, readiness_probe, and http_get keys are all invalid.

lifecyclrotten

Source

RochesterinNYC

👍3

Most helpful comment

I'm not sure if this is canonical, but this is my approach to a similar situation.

from kubernetes.client import ApiClient
api = ApiClient()
api.sanitize_for_serialization(deploymemnt_resource)

This will create a dict.

allanadair on 16 Nov 2017

👍6 ❤3

All 6 comments

I'm not sure if this is canonical, but this is my approach to a similar situation.

from kubernetes.client import ApiClient
api = ApiClient()
api.sanitize_for_serialization(deploymemnt_resource)

This will create a dict.

allanadair on 16 Nov 2017

👍6 ❤3

https://github.com/kubernetes-client/python/issues/683#issuecomment-456082546

@allanadair your workaround is working, thanks

gree-gorey on 21 Jan 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 28 Apr 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 28 May 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 27 Jun 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.