Skip to content

Stop talking to the kubelet unsecured port #3242

Open
@bboreham

Description

When running under Kubernetes, the probe will try to talk to kubelet on 10255, unsecured, if it doesn't know the node name. We should not assume unsecured access.

There is a secured port at 10250; probably we have access to credentials. Or we could just remove that code and insist on knowing the node name.

Kubeadm removes the unsecured port by default: kubernetes/kubernetes#64187

This is possibly the underlying issue for #3104 (OpenShift)

Metadata

Assignees

No one assigned

    Labels

    choreRelated to fix/refinement/improvement of end user or new/existing developer functionalityestimate/hoursIt will take less than 8 hours to implementgood-first-issueIndicates a good issue for first-time contributorshelp-wantedAn issue that would be good for non-maintainers to attemptk8sPertains to integration with Kubernetes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions