Update discovery installers to work with zypper

[lxea]

This updates the automatic server discovery scripts to work with zypper

As it stands it hard-codes that its using the RHEL v8 teleport RPM repo, though I'm not sure if this is the best idea, and if we should instead host suse specific RPMs

Part of #29267

[r0mant]

Can you update auto-upgrades and Discover install scripts as well?

[lxea]

Can you update auto-upgrades and Discover install scripts as well?

The discovery scripts are the ones updated here, are there other ones?

The auto-upgrades script is in e so i'll do that in a separate PR

[lxea]

Is there a reason we're using $OSTYPE rather than checking against uname ? It seems more portable and works on macos too.

opensuse defines OSTYPE as linux, ubuntu defines it as linux-gnu and alpine (for example) doesn't define it, where as uname is just Linux on all of them

[strideynet]

👍 I'm happy with this as is - especially since thats currently how it is - but it'd be nice to see us use uname instead.

[r0mant]

@lxea By Discover I meant the node-join script that users download via Teleport Discover interface (when you click on add a server resource for example): https://github.com/gravitational/teleport/blob/master/lib/web/scripts/node-join/install.sh.

[ibeckermayer]

LGTM in terms of bash script fundamentals, the details are beyond my understanding

[r0mant]

@lxea Let's hold this off until @fheinecke adds the SUSE channel so we can remove RHEL version hardcodes from the scripts.

[r0mant]

@fheinecke IIRC you set up the zypper repository and was going to configure a separate DNS name for it. Is it done now, can we update this PR?

[fheinecke]

@r0mant Yes it is. I haven't had a chance to file doc PRs for the changes but an install example is available in our smoke tests here.

Note that prior to these two lines the user will need to run sudo rpm --import "https://zypper.releases.teleport.dev/gpg" to import the signing key.

[r0mant]

@lxea Have you tested these changes for all 3 use-cases?

• Automatic upgrade script
• Discover install script
• Auto-discovery install script

[lxea]

@lxea Have you tested these changes for all 3 use-cases?

* [x]  Automatic upgrade script

* [x]  Discover install script

* [x]  Auto-discovery install script

Yeah, all of these appear to be working, tried on a fresh AWS SLES instance

[strideynet]

👍 I'm happy with this as is - especially since thats currently how it is - but it'd be nice to see us use uname instead.

[public-teleport-github-review-bot]

@lxea See the table below for backport results.

Branch	Result
branch/v13	Create PR