-
Notifications
You must be signed in to change notification settings - Fork 73
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
Try out GKE Autopilot #259
Comments
gcsfuse uses hostpath mapping in write mode. |
we had an alternative to hostpath but that was too expensive, right?
…On Fri, Mar 19, 2021 at 7:55 AM sirdarckcat ***@***.***> wrote:
https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#host_options_restrictions
gcsfuse uses hostpath mapping in write mode.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#259 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM2JHSK7CBES6VGAUOQ4JTTELYPPANCNFSM4ZB3R2IA>
.
|
it also uses |
to use fuse without priv we would need this: moby/moby#41880 apiVersion: apps/v1
kind: Deployment
metadata:
name: foo-deployment
labels:
app: foo
spec:
replicas: 1
selector:
matchLabels:
app: foo
template:
metadata:
labels:
app: foo
annotations:
container.apparmor.security.beta.kubernetes.io/foo: unconfined
spec:
containers:
- name: foo
image: ubuntu:latest
command: ['/bin/bash']
args: ["-c", "sleep 1d"]
securityContext:
procMount: UnmaskedProcMount
seccompProfile:
type: Unconfined
volumeMounts:
- name: dev-dir
mountPath: /dev
volumes:
- name: dev-dir
hostPath:
path: /dev I guess we need to choose between autopilot and gcsfuse. |
In that case we should stick with gcsfuse unless we find some good
alternative.
Maybe revisit in 6-12 months?
…On Fri, Mar 19, 2021 at 12:19 PM sirdarckcat ***@***.***> wrote:
to use fuse without priv we would need this: moby/moby#41880
<moby/moby#41880>
apiVersion: apps/v1kind: Deploymentmetadata:
name: foo-deployment
labels:
app: foospec:
replicas: 1
selector:
matchLabels:
app: foo
template:
metadata:
labels:
app: foo
annotations:
container.apparmor.security.beta.kubernetes.io/foo: unconfined
spec:
containers:
- name: foo
image: ubuntu:latest
command: ['/bin/bash']
args: ["-c", "sleep 1d"]
securityContext:
procMount: UnmaskedProcMount
seccompProfile:
type: Unconfined
volumeMounts:
- name: dev-dir
mountPath: /dev
volumes:
- name: dev-dir
hostPath:
path: /dev
I guess we need to choose between autopilot and gcsfuse.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#259 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM2JHUBN5QPNAVMBPFFMCTTEMXM3ANCNFSM4ZB3R2IA>
.
|
lets do that, yea. I'll leave this open. |
Curious if there were any updates or progress on this? Autopilot looks pretty cool for a Kubernetes newb. |
it is really cool! it doesn't completely work due to our use of hostPath,
so we would most likely need to find another way to do persistent storage.
… |
I think they use hostPath, yes
|
It was suggested in GoogleCloudPlatform/gcsfuse#497 that csi-gcs could be used. |
Ah yes, that would work!
…On Fri, 29 Oct 2021, 15:30 ElJeffe, ***@***.***> wrote:
It was suggested in GoogleCloudPlatform/gcsfuse#497
<GoogleCloudPlatform/gcsfuse#497> that csi-gcs
<https://github.com/ofek/csi-gcs> could be used.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#259 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAICQIMNWANN7PAO4FVKEDUJKOVVANCNFSM4ZB3R2IA>
.
|
Holly $h**, KCTF in the Cloud is expensive. I had started the cloud walkthrough a couple weeks ago. Didn't realize that Google Cloud charges you for spinning it up. Got a bill today and it wasn't cheap. There should be a warning on the setup for those Compute Engines. Ouch |
Oh, submit a ticket. Cloud Support might refund you.
|
It appears autopilot doesn't allow pods with SYS_ADMIN capability to be admitted, so we wouldn't be able to isolate tasks. |
(context: sys_admin is required for using |
Ah we can change the default policy |
https://cloud.google.com/blog/products/containers-kubernetes/introducing-gke-autopilot
The text was updated successfully, but these errors were encountered: