Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to define user/password to log in to cluster nodes via IPMI #358

Open
jmencak opened this issue Jun 8, 2023 · 0 comments
Open

Comments

@jmencak
Copy link

jmencak commented Jun 8, 2023

This is a feature request. When facing network issues, it is useful to log in to cluster nodes via IPMI to debug. This should ideally be done on two levels:

  1. Prior to installation by modifying the installation media to debug installation failures.
  2. Post-installation by creating MachineConfig manifests.

I believe the first could be achieved by using the quay.io/coreos/coreos-installer:release. Here is an example how to do this.

The latter could be done by users themselves by supplying a MachineConfig manifest. The following will work on SNO, for other clusters another label targetting all cluster nodes would have to be used.

apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: master
  name: 40-password-core
spec:
  config:
    ignition:
      version: 3.2.0
    passwd:
      users:
      - name: core
        passwordHash: <password-hash-removed>

An aside: applying this manifest on recent OCP versions will not even reboot the cluster node.

I believe this could be done in one of two ways:

  1. By supplying ignition files to be embedded into the installation media and adding MachineConfig manifests from a manifests directory the way it is done by the bootstrap-in-place-poc.
  2. By letting users to configure a user/password combination.

The former approach is more flexible and will solve many other issues/requests users of this tooling have, the latter is probably more novice user friendly.

Perhaps we could start by copying the approach taken by bootstrap-in-place-poc and then add the user/password option as an abstraction on top of it.

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant