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 handful of examples for the various charts #331

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

colearendt
Copy link
Contributor

We add an example for each product using sqlite (with NOT NFS), and an example of Connect using a sidecar sssd so that a dedicated Connect build is not required.

We should really test that these examples work before we add them to the repo

We add an example for each product using sqlite (with NOT NFS),
and an example of Connect using a sidecar sssd so that a dedicated
Connect build is not required.
@colearendt colearendt requested review from a team and atheriel as code owners January 24, 2023 15:09
Comment on lines +6 to +41
volumes:
- name: sssd-emptydir
emptyDir: {}
- name: sssd-config
configMap:
name: sssd-config
defaultMode: 0600
- name: pam-config
configMap:
name: pam-config
defaultMode: 0755
volumeMounts:
- name: sssd-emptydir
mountPath: /var/lib/sss
- name: pam-config
mountPath: /etc/pam.d/common-account
subPath: common-account
- name: pam-config
mountPath: /etc/pam.d/common-session
subPath: common-session
- name: pam-config
mountPath: /etc/pam.d/common-auth
subPath: common-auth
- name: pam-config
mountPath: /etc/pam.d/common-password
subPath: common-password
sidecar:
- name: sssd
image: "some-sssd-image"
imagePullPolicy: "IfNotPresent"
securityContext: {}
volumeMounts:
- name: sssd-emptydir
mountPath: /var/lib/sss
- name: sssd-config
mountPath: /etc/sssd/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might be able to use this pattern to support runAsCurrent user with off-host execution. I don't think it would require any changes to Connect since we already assume uid/gid/passwd consistency between Connect and the content Pod.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😮 That's pretty cool!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aronatkins pointed out that rsandbox/PAM password forwarding might pose a problem here, but it's worth a spike to see how far this gets us and if there are any other limitations.

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

Successfully merging this pull request may close these issues.

2 participants