Replies: 2 comments 7 replies
-
|
/cc @Sgitario (kubernetes), @geoand (kubernetes,openshift), @iocanel (kubernetes,openshift) |
Beta Was this translation helpful? Give feedback.
-
|
I think I see what is going here. You need to incorporate your ConfigMap and Secret resources into the generated apiVersion: v1
kind: ConfigMap
metadata:
name: my-config-map
data:
db-url: jdbc:postgresql://postgresql/databasename
---
apiVersion: v1
kind: Secret
metadata:
name: my-secret
type: Opaque
data:
db-username: username
db-password: passwordAnd then copy this More information about this here: https://quarkus.io/guides/deploying-to-kubernetes#using-common-resources |
Beta Was this translation helpful? Give feedback.
-
|
I still can't deploy the app. I have created the common.yml file as you have told me, and I see that when I do the build it includes that inside the openshift.yml. But when I display the image in opneshift it tells me the following:
The values inside the secret are encoded in base64 |
Beta Was this translation helpful? Give feedback.
-
|
If the secret data values are encoded, it should work fine. I tried it myself and everything did. Note that I'm using the Kubernetes extension, but it should not really matter. My generated ---
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
app.quarkus.io/build-timestamp: 2023-03-02 - 11:37:23 +0000
labels:
app.kubernetes.io/version: 1.0.0-SNAPSHOT
app.kubernetes.io/name: code-with-quarkus
name: code-with-quarkus
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/version: 1.0.0-SNAPSHOT
app.kubernetes.io/name: code-with-quarkus
template:
metadata:
annotations:
app.quarkus.io/build-timestamp: 2023-03-02 - 11:37:23 +0000
labels:
app.kubernetes.io/version: 1.0.0-SNAPSHOT
app.kubernetes.io/name: code-with-quarkus
spec:
containers:
- env:
- name: KUBERNETES_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POSTGRESQL_PASSWORD
valueFrom:
secretKeyRef:
key: POSTGRESQL_PASSWORD
name: my-secret
- name: POSTGRESQL_URL
valueFrom:
secretKeyRef:
key: POSTGRESQL_URL
name: my-secret
- name: POSTGRESQL_USERNAME
valueFrom:
secretKeyRef:
key: POSTGRESQL_USERNAME
name: my-secret
image: quay.io/jcarvaja/quarkus-example:latest
imagePullPolicy: Always
name: code-with-quarkus
ports:
- containerPort: 8080
name: http
protocol: TCP
---
apiVersion: v1
kind: Secret
metadata:
name: my-secret
data:
POSTGRESQL_URL: amRiYzpwb3N0Z3Jlc3FsOi8vcG9zdGdyZXM6NTQzMi9leGFtcGxl
POSTGRESQL_USERNAME: dXNlcg==
POSTGRESQL_PASSWORD: cGFzcw==
type: Opaque
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: postgres
spec:
replicas: 1
selector:
matchLabels:
service: postgres
template:
metadata:
labels:
service: postgres
spec:
containers:
- env:
- name: POSTGRES_DB
value: example
- name: POSTGRES_USER
value: user
- name: POSTGRES_PASSWORD
value: pass
image: postgres:15.1
name: postgres
ports:
- containerPort: 5432
---
apiVersion: v1
kind: Service
metadata:
name: postgres
spec:
ports:
- port: 5432
selector:
service: postgres
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
annotations:
app.quarkus.io/build-timestamp: 2023-03-02 - 11:37:23 +0000
labels:
app.kubernetes.io/name: code-with-quarkus
app.kubernetes.io/version: 1.0.0-SNAPSHOT
name: code-with-quarkus
spec:
ports:
- name: http
port: 80
protocol: TCP
targetPort: 8080
selector:
app.kubernetes.io/name: code-with-quarkus
app.kubernetes.io/version: 1.0.0-SNAPSHOT
type: ClusterIP
|
Beta Was this translation helpful? Give feedback.
-
|
I have tried to display your code and it gives me an error. I generate the image fine...but when I deploy it in openshift it gives me the following error: The only thing I do is upload the image to docker hub, and deploy said image from openshift. When I deploy the image with the values entered directly in the properties file, it deploys correctly. Apart from this, your solution would not work for me, because I am not going to know the information contained in the secrets. That should be put by the client in the openshift directly without going through me. They ask me to upload the image, and they configure the secret in the openshift. Is this possible? |
Beta Was this translation helpful? Give feedback.
-
This is happening because Quarkus can't resolve the data source properties. Somehow, OpenShift/Kubernetes is not getting the env var values from the secret and the configMap. Double-check that the deploymentConfig definition is correct and these resources are installed in the same namespace.
Yes, of course. The only thing you need to be aware of is that the secret and config map resources should be installed within the same namespace before installing your application. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, the example worked fine for me, but I created the secret and configmap by hand (using something like: [1]) @Sgitario should work too. [1]: kubectl create secret generic my-secret --from-literal=db-username=postgres --from-literal=db-password= |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to deploy my quarkus application in Openshift. I am trying to make the connection to the database with some environment variables whose value will be indicated in a configmap file and in a secrets file.
I have a my-configmap.yaml like:
I also have a my-secret.yaml:
My application.properties file:
I have tried in several ways (quarkus.kubernetes.env... instead of quarkus.openshift.env) but I can't get it to work. I have also tried to create a deployment config from openshift in which I indicate the environment variables but nothing.
What am I doing wrong or how can I do it?
Beta Was this translation helpful? Give feedback.
All reactions