Modify a ConfigMap value with k8s_json_patch #566
Comments
|
@jgagnon44 A ConfigMap is just key/value data. It's not structured. The path |
|
OK. I was suspecting something along these lines, but wasn't sure. I'm very new to Ansible. How could I pull the |
|
I would probably do something like: - hosts: localhost
gather_facts: false
tasks:
- kubernetes.core.k8s:
kind: Namespace
name: testing
- kubernetes.core.k8s:
definition:
apiVersion: v1
kind: ConfigMap
metadata:
name: test-map
namespace: testing
data:
config.conf: |
apiVersion: v1
kind: Pod
metadata:
name: my-pod
- kubernetes.core.k8s_info:
kind: ConfigMap
name: test-map
namespace: testing
register: result
- set_fact:
new_data: "{{ result.resources[0].data['config.conf'] | from_yaml | combine(patch, recursive=true) }}"
vars:
patch:
kind: Secret
metadata:
namespace: some-ns
- kubernetes.core.k8s_json_patch:
kind: ConfigMap
name: test-map
namespace: testing
patch:
- op: replace
path: /data/config.conf
value: "{{ new_data | to_nice_yaml(indent=2) }}"Do note the limitation with string width: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_filters.html#formatting-data-yaml-and-json. |
|
Took me a bit, but got it work. Thanks. |
SUMMARY
Getting "422 - Unprocessable Entity" when attempting to modify ConfigMap.
I am wondering if the issue is related to the unique representation of the ConfigMap data. I am not sure if I using the correct path to the element of interest.
For example, the ConfigMap I'm attempting to modify, appears as follows when rendered as JSON:
{ "apiVersion": "v1", "data": { "config.conf": "apiVersion: kubeproxy.config.k8s.io/v1alpha1\nbindAddress: 0.0.0.0\nbindAddressHardFail: false\nclientConnection:\n acceptContentTypes: \"\"\n burst: 0\n contentType: \"\"\n kubeconfig: /var/lib/kube-proxy/kubeconfig.conf\n qps: 0\nclusterCIDR: \"\"\nconfigSyncPeriod: 0s\nconntrack:\n maxPerCore: null\n min: null\n tcpCloseWaitTimeout: null\n tcpEstablishedTimeout: null\ndetectLocal:\n bridgeInterface: \"\"\n interfaceNamePrefix: \"\"\ndetectLocalMode: \"\"\nenableProfiling: false\nhealthzBindAddress: \"\"\nhostnameOverride: \"\"\niptables:\n masqueradeAll: false\n masqueradeBit: null\n minSyncPeriod: 0s\n syncPeriod: 0s\nipvs:\n excludeCIDRs: null\n minSyncPeriod: 0s\n scheduler: \"\"\n strictARP: false\n syncPeriod: 0s\n tcpFinTimeout: 0s\n tcpTimeout: 0s\n udpTimeout: 0s\nkind: KubeProxyConfiguration\nmetricsBindAddress: 0.0.0.0\nmode: \"\"\nnodePortAddresses: null\noomScoreAdj: null\nportRange: \"\"\nshowHiddenMetricsForVersion: \"\"\nudpIdleTimeout: 0s\nwinkernel:\n enableDSR: false\n forwardHealthCheckVip: false\n networkName: \"\"\n rootHnsEndpointName: \"\"\n sourceVip: \"\"", "kubeconfig.conf": "apiVersion: v1\nkind: Config\nclusters:\n- cluster:\n certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt\n server: https://172.20.8.68:6443\n name: default\ncontexts:\n- context:\n cluster: default\n namespace: default\n user: default\n name: default\ncurrent-context: default\nusers:\n- name: default\n user:\n tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token" }, "kind": "ConfigMap", "metadata": { "annotations": { "kubeadm.kubernetes.io/component-config.hash": "sha256:aa87680dfe2321f98df103555d18d439916b19e0bf23bd0f98bb3e27c5adfc08" }, "creationTimestamp": "2022-08-22T12:08:21Z", "labels": { "app": "kube-proxy" }, "name": "kube-proxy", "namespace": "kube-system", "resourceVersion": "21706920", "uid": "97594de0-5aaa-4ea0-bd8c-a2f5fb357be7" } }ISSUE TYPE
COMPONENT NAME
kubernetes.core.k8s_json_patch
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
"Launch" computer:
Windows 11 21H2, OS build: 22000.1455
Ansible "node":
Docker image: cytopia/ansible:latest-tools
Linux ec1303bf69ab 5.10.104-linuxkit #1 SMP Thu Mar 17 17:08:06 UTC 2022 x86_64 Linux
Kubernetes node (control plane):
Linux gagnon-m1 5.4.0-126-generic #142-Ubuntu SMP Fri Aug 26 12:12:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
STEPS TO REPRODUCE
This is being run via a Docker image that contains an Ansible installation. I am running the container and then inside the container, running the playbook. The commands below summarize the process.
In the container:
EXPECTED RESULTS
The
metricsBindAddressin theconfig.confentry in theConfigMapdata to be changed to0.0.0.0.ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: