You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The core issue is the parsing and output into JSON from proto buffers stripping default fields.
The solution would be to update the CRD to include the Status field and use the /status update endpoint available from Kubernetes 1.11 API to ensure just the Status fields are updated. We will need to wait until the k8s Java client includes this support or we add it.
We would need to check the version of k8s running to be >= 1.11 for this to be used otherwise we would need to fallback to updating the whole CR object when updating the status.
to check the version in java
VersionApi apiInstance = new VersionApi(client);
try {
VersionInfo result = apiInstance.getCode();
System.out.println(result);
} catch (ApiException e) {
System.err.println("Exception when calling VersionApi#getCode");
e.printStackTrace();
}
How to reproduce:
A diff of the two manifests will show the children field as missing.
Tools that provision deployments (eg argocd) will see the difference as an out of sync deployment.
The text was updated successfully, but these errors were encountered: