Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
f
freezing-summer-64950
08/02/2022, 4:59 PMHas anyone successfully deployed nexus with helm into K3s and exposed it to be accessible on a web browser ? I have nexus pods running but the web app is not accessible yet...unsure if it's a load balancer issue with traefik or if I need to install nginx
s
steep-furniture-72588
08/02/2022, 6:36 PMi am using nexus. whats the image and set up that you used?
f
freezing-summer-64950
08/02/2022, 11:23 PMI used helm to deploy nexus 3.X with a deployment.yAml and service.yaml https://developer.entando.com/v6.2/tutorials/ecr/how-to-setup-nexus-on-kubernetes-cluster.html#steps
s
steep-furniture-72588
08/03/2022, 4:06 PMwhats the error and whats your actual yaml that you used?
f
freezing-summer-64950
08/03/2022, 6:28 PMI don't have an error..it's not being exposed when I'm trying to access nexus from the url address..the yaml is the same from the link
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: nexus
namespace: nexus
spec:
replicas: 1
selector:
matchLabels:
app: nexus-server
template:
metadata:
labels:
app: nexus-server
spec:
containers:
◦ name: nexus
image: sonatype/nexus3:latest
resources:
limits:
memory: "4Gi"
cpu: "1000m"
requests:
memory: "2Gi"
cpu: "500m"
ports:
◦ containerPort: 8081
volumeMounts:
◦ name: nexus-data
mountPath: /nexus-data
volumes:
◦ name: nexus-data
emptyDir: {}
apiVersion: v1
kind: Service
metadata:
name: nexus-service
namespace: devops-tools
annotations:
prometheus.io/scrape: 'true'
prometheus.io/path: /
prometheus.io/port: '8081'
spec:
selector:
app: nexus-server
type: NodePort
ports:
◦ port: 8081
targetPort: 8081
nodePort: 32000
Just curious if the docker image needs to be build prior to helm deploy
s
steep-furniture-72588
08/04/2022, 6:18 AMok. whats in the conmtyainer log? it can take abit to start
initially
whats the url adddress and does that match to the node it sits on?
no need to provide adddress but would still like to sddfress second questoion
f
freezing-summer-64950
08/05/2022, 1:05 AMI disabled traefik and helm installed nginx as the Ingres controller...the nexus pod spinned up but I'll have to fetch the container log and I'll post it later today or by tomorrow morning
Are u referring to the node cluster ip? Or rancher node domain name ?
s
steep-furniture-72588
08/05/2022, 10:55 PMthe cluster ip cannot be rteached by the outside worldf
are yoiu putting in the node ip?
f
freezing-summer-64950
08/06/2022, 5:06 AMAre you referencing the master or worker node ip that's it's deployed in?
It's just stuck at initializing within the UI from the above screenshot