The first thing about the secrets file is that every value needs to be a Base64 Encoded version of itself so:
The second thing (to address your question about the database endpoint) is that the examples make use of the Mendix docker build pack and the format used for postgres there is:
So from the example will be:
I’ve used the name of the postgres service in postgres-service.yaml for the host, I’m not sure if this is correct but it worked for me.
Hopefully this gets you past your issue.
Additionally, if you are doing this as a local test without a Mendix license key, you can leave license-key and license-id empty:
apiVersion: v1 kind: Secret metadata: name: mendix-app-secrets type: Opaque data: admin-password: SomePasswordBase64Encoded db-endpoint: cG9zdGdyZXM6Ly9tZW5kaXg6bWVuZGl4QHBvc3RncmVzLXNlcnZpY2U6NTQzMi9kYjA= license-key: license-id:
If you do this you’ll need to run the secret creation without validation:
kubectl create -f mendix-app-secrets.yaml --validate=false
I have never deployed Mendix this way myself, but it seems to me that you should be putting the ip/port of your database in place of YOUR_DATABASE_ENDPOINT. Though it’s not clear to me (from the documentation) where you would get that info from.