obj.metadata.selfLink is always None about hikaru HOT 3 CLOSED

I don't think you've found a bug here, I think you're stubbing your toe on a planned Kubernetes deprecation. Looking at the pure K8s client Deployment object in the debugger (V1Deployment), it also shows a None for self_link (which Hikaru knows to map to selfLink), so Hikaru isn't being handed anything useful on my testbed.

Further, this Kubernetes issue from Jul 2019, kubernetes/enhancements#1164, says that selfLink is to be deprecated. It's unclear as to the timing of that, but the availability of the field is probably dependent on the version of the server you're running, and perhaps the version of the underlying K8s Python client. My k3s infra says it's following 1.20 which is well in the range where the field would no longer be provided. Even if it was previously populated it sounds like it's a bad idea to rely on it since it's targeted for deprecation. I'll leave this open until I hear back from you, but my inclination is to close this issue.

from hikaru.

I'll close this tomorrow unless I hear otherwise.

from hikaru.

Hi, you can close this. You're correct about the deprecation. I can confirm on my own cluster that selfLink no longer exists by running kubectl get deployment -o yaml.

As an aside, here is what tripped me up: When I originally opened this issue I first verified that selfLink existed on my cluster and was only missing from Hikaru... But I performed the check using the Lens client and apparently Lens is patching in selfLink even when it doesn't exist on the API Server. See https://github.com/lensapp/lens/pull/1804/files

from hikaru.