First iteration of a server container image #7619
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cbosdo
requested review from
wweellddeerr and
agraul
and removed request for
a team
cbosdo
force-pushed
the
server-container
branch
2 times, most recently
from
ae33c65
to
be626fb
Compare
cbosdo
force-pushed
the
server-container
branch
6 times, most recently
from
064d6aa
to
eee5c1c
Compare
deneb-alpha
reviewed
Oct 5, 2023
deneb-alpha
reviewed
Oct 5, 2023
deneb-alpha
reviewed
Oct 5, 2023
deneb-alpha
reviewed
Oct 5, 2023
cbosdo
force-pushed
the
server-container
branch
3 times, most recently
from
9bb7bc0
to
86581b7
Compare
This image is not needed for SUSE Manager as the BCI:Init image will be used instead. Changed the push-packages-to-obs.sh to ignore it there.
Uses uyunictl to deploy on a server container running either in kubernetes or on podman.
Provide a helm chart to ease installation of the server container on kubernetes cluster.
Signed-off-by: Ricardo Mateus <rmateus@suse.com>
In the kubernetes container the SSL connection is stopped at the ingress level so localhost doesn't handle HTTPS.
In some cases mgr-sync seems to wait for ever for the user / password on the input provided by `echo -e`. Using the `~/.mgr-sync` configuration file is more reliable.
- UID and GIDs are made to match each other if possible - IDs starts at 10550 to prevent conflicts with host system accounts - postgres has to have login shell, required during configuration
Running the redfish mocked server on the server would require exposing the 8443 port on the container, which is impossible when the pod is running, and not desirable. Moving the fake server to the controller works around this issue.
cbosdo
force-pushed
the
server-container
branch
from
86581b7
to
fddce9d
Compare
|
acceptance tests pass now. I do not know what was that segmentation fault. |
jordimassaguerpla
approved these changes
Oct 10, 2023
|
|
sbluhm
added a commit
to sbluhm/uyuni-repo
that referenced
this pull request
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Image, helm chart, setup and testsuite changes to run the server in a podman or kubernetes container.
GUI diff
Not really GUI, but the tooling required to deploy and interact with the server is changing. The https://github.com/uyuni-project/uyuni-tools will be used with the container.
Documentation
Documentation issue was created: Document how to use the containerized server uyuni-docs#2488
DONE
Test coverage
Cucumber tests CI are now running also for podman and k3s container hosts.
DONE
Links
Fixes #
Tracks # add downstream PR, if any
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run: