After deploying plesk in Kubernetes Engine (GKE) It redirecting me to login page again and again
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, gcp, kubernetes
- Domain
- cloud, infrastructure
Research direction
Start by applying the provided Kubernetes Deployment and Service manifest in GKE and reproducing the repeated login redirect. Inspect the Plesk container behavior and deployment configuration to identify what prevents a session from persisting; done means documenting a verified configuration change that allows login to remain active.
Written by the indexing model from the issue text.
Description
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: plesk-deployment
labels:
app: plesk
spec:
replicas: 2
selector:
matchLabels:
app: plesk
template:
metadata:
labels:
app: plesk
spec:
containers:
- name: plesk
image: gcr.io/gcp-tech/plesk:version1
# imagePullPolicy: Always
securityContext:
privileged: true
ports:
- containerPort: 8880
volumeMounts:
- mountPath: /sys/fs/cgroup
name: cgroup
readOnly: true
- mountPath: /tmp
name: tmpfs
- mountPath: /run
name: tmpfs
- mountPath: /run/lock
name: tmpfs
volumes:
- name: tmpfs
emptyDir: {}
- name: cgroup
hostPath:
path: "/sys/fs/cgroup"
type: Directory
---
apiVersion: v1
kind: Service
metadata:
name: plesk-Service
spec:
selector:
app: plesk
ports:
- protocol: TCP
port: 8880
targetPort: 8880
type: LoadBalancer```- Dominant language
- Dockerfile
- Stars
- 98
- Forks
- 49
- Avg merge
- 57m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plesk/docker
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
transitmatters/t-performance-dash#1217 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
tailscale/go-cache-plugin#25 ·
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/product-integrator-mi#5061 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days