chore(krb5-testing-tools): Rename image

[NickLarsenNZ]

Caution

Blocking this on #1224 so I don't cause extra merge conflicts while it is in review.

The image is not part of the SDP platform, so I recommend we move it to the correct Harbor project, and rename the image so indicate its usage.

Tip

Update image references in ad-init and hdfs-topology-provider, hdfs-utils, demos. Be sure to use Harbor and the correct project (stackable instead of sdp).

[NickLarsenNZ]

Note, there are other images that should also be move to the stackable project in Harbor:

• kafka-testing-tools
• testing-tools
• maybe trino-cli

[NickLarsenNZ]

The image builds:

 => => exporting layers                                                                                                                                                                                                                                            1.2s
 => => writing image sha256:663584d2fea34c2aa6cce1052521b1eab2bab59118700d63ef521bd59f9c6519                                                                                                                                                                       0.0s 
 => => naming to oci.stackable.tech/sdp/krb5-testing-tools:1.21.1-stackable0.0.0-dev

[nightkr]

krb5-testing-server maybe? Traditionally we've reserved -tools for "toolbox images" rather than daemons.

[NickLarsenNZ]

krb5-testing-server maybe? Traditionally we've reserved -tools for "toolbox images" rather than daemons.

I was going to call it -server until I saw it being used as a client (and not server) in a container.

https://github.com/stackabletech/hdfs-topology-provider/blob/3a865217f134f816f915c2266ef1a233c0b7e753/test/stack/01-install-krb5-kdc.yaml#L80-L89

I don't mind though.

[nightkr]

Ah, right. For some reason I thought we set CMD. We don't, so -tools should be fine after all ("server is one role it can take, but not the default").

[NickLarsenNZ]

I'll raise the PRs (ad-init, hdfs-topology-provider, hdfs-utils, demos) before merging this

• chore: Use renamed krb5-testing-tools image ad-init#6
• todo: hdfs-utils
• todo: demos

[nightkr]

We use it in demos too, right?

[NickLarsenNZ]

I'll take another look, but I didn't see a usage.

[nightkr]

https://github.com/stackabletech/demos/blob/088256b88b73d26b0c7bba0c380c55fd43e33530/stacks/end-to-end-security/krb5.yaml#L17

[NickLarsenNZ]

Ah yeah... so it's name is kind of bad.
We'll think of an alternative name - otherwise I'll drop the PR.

[NickLarsenNZ]

@sbernauer and I chatted about potential naming this morning, as it is used in:

• tests
• demos

For:

• non-prod KDC's
• krb5 client tools

Considering that, we feel krb5-testing-tools isn't exactly correct. I did consider dropping the PR, but I still stand by my original reasoning that krb5 on its own misses some signals about what it is and were it could be used (or shouldn't be used - which, sure, is explained in the docs I updated here)

---

Name ideas

• krb5-nonprod (signals do not use in Production)
• krb5-kdc (signals it can be used as a KDC... but then it can also be used for the client tools)

[sbernauer]

Staying with krb5 and krb5-nonprod both LGTM 👍