This is not possible due to security restrictions.
The functionality of OpenShift and all involved services are completely monitored and operated by VSHN. Individual projects are not monitored out of the box - but Kubernetes already has health checks integrated and running. Also replication controllers make sure that Pods are running all the time. If you need a more complex monitoring for your project, feel free to contact us under support.
More information can also be found here: Application Health
We backup all data relevant to run the OpenShift cluster. Application data itself is not in the default backup and is the responsibility of the user. However we can provide a backup service for individual projects. Please contact us under support for more information.
When creating an application route, the platform automatically generates a URL
which is immediately accessible, f.e. http://django-psql-example-my-project.appuioapp.ch
due to wildcard DNS entries under *.appuioapp.ch
. If you now want to have this application
available under your own custom domain, follow these steps:
- Edit the route and change the hostname to your desired hostname, f.e.
www.myapp.ch
- Point your DNS entry using a CNAME resource record type (important!) to
cname.appuioapp.ch
Always create a route before pointing a DNS entry to APPUiO, otherwise someone else could create a matchting route and serve content under your domain.
Note that you can't use CNAME records in the apex domain (example.com, e.g. without www in front of it). If you need to use the apex domain for your application you have the following options:
- Redirect to a subdomain (e.g. example.com -> www.example.com or app.example.com) with your DNS-provider, set up the subdomain with a CNAME
- Use ALIAS-records with your DNS-provider if they support them
- Enter 5.102.151.2 and 5.102.151.3 as A records
Disclaimer: These addresses may change at any time. We do not recommend whitelisting by IP address. A better option is to use Transport Layer Security (TLS) with client certificates for authentication.
- Incoming connections for routes
5.102.151.2
,5.102.151.3
- Outgoing connections from pods
5.102.147.130
,5.102.147.124
,2a06:c00:10:bc00::/56
OpenShift supports secure routes and everything is prepared on APPUiO to have
it secured easily. Just edit the route and change the termination type to edge
.
There is a default trusted certificate in place for *.appuioapp.ch
which is
used in this case. If you want to use your own certificate, see Routes.
We provide shared persistent storage using GlusterFS. Please make sure that the database intended to use is capable
of storing it's data on a shared filesystem. We don't recommend running production databases with GlusterFS as
storage backend. If you don't fear it, we strongly urge you to at least have a regular database dump available.
On https://github.com/appuio?q=backup
you can find some database dump applications.
For highly-available and high-performance managed databases, please contact the APPUiO team under hello.
I get an error like 'Failed Mount: MountVolume.NewMounter initialization failed for volume "gluster-pv123" : endpoints "glusterfs-cluster" not found'
When you received your account there was a service called "glusterfs-cluster" pointing to the persistent storage endpoint. If you delete it by accident you can re-create it with:
oc create -f - <<EOF apiVersion: template.openshift.io/v1 kind: List items: - apiVersion: v1 kind: Service metadata: name: glusterfs-cluster spec: ports: - port: 1 protocol: TCP targetPort: 1 - apiVersion: v1 kind: Endpoints metadata: name: glusterfs-cluster subsets: - addresses: - ip: 172.17.176.30 - ip: 172.17.176.31 - ip: 172.17.176.32 ports: - port: 1 protocol: TCP EOF
Or copy the YAML between "oc" and "EOF" in the Web-GUI to "Add to project" -> "Import YAML/JSON"
Or run oc create -f https://raw.githubusercontent.com/appuio/docs/master/glusterfs-cluster.yaml
Please note that the IP addresses above are dependent on which cluster you are on, these are valid for console.appuio.ch