Installing epinio is not so simple - https://docs.epinio.io/installation#installation. What should I do if I want to deploy it top of a k3s cluster installed - https://rancher.com/docs/rancher/v2.6/en/quick-start-guide/deployment/quickstart-manual-setup/ ?

I got an error when I try to do

epinio push

-->

epinio push --name sample --path sample-app

🚢  About to push an application with the given setup
Manifest: <<Defaults>>
Name: sample
Source Origin: /home/snowdrop/epinio/assets/sample-app
Target Namespace: workspace

⚠️  Hit Enter to continue or Ctrl+C to abort (deployment will continue automatically in 5 seconds)

Create the application resource ...
2022/05/13 12:46:15 EpinioApiClient: "msg"="request failed" "error"="Post \"/api/v1/namespaces/workspace/applications\": unsupported protocol scheme \"\""

❌  error pushing app to server: making the request: Post "/api/v1/namespaces/workspace/applications": unsupported protocol scheme ""

Will the Epinio UI be merged within the next version of the Rancher UI?

Can we define which k8s manifests epinio should deploy when a new application is installed ?

Followed the latest instructions for epinio install on rancher-deskstop Used the paketo project for my source to try out things. The push stalled out on staging. So here are some of the commands I did to try and determine what was wrong

Is epinio rio.io successor?

Could I just use an image to host an app on epinio? And bypass the buidpack step, is that what --container-image-url provide?

Is there a way to change the DNS after epinio installation?

Nice blog post from @high-morning-12231: https://www.suse.com/c/rancher_blog/customizing-your-application-with-epinio/

If you are interested in discussing about Epinio in person, join us today for a chat: https://susecon2022.braindate.com/topics/84175/ . Only a few spots left.

hey y'all, having a little bit of trouble understanding the helm install options when installing into a downstream Rancher cluster, and have a few questions API Username: Are we creating this? Or is this an existing username? API Password: Are we creating this? Or is this an existing password? Access control allow origin: Is this the global rancher cluster dashboard or the cluster explorer link? (for example, https://cluster.krum.io/?, https://cluster.krum.io/dashboard/?, https://cluster.krum.io/dashboard/c/c-123456/?)

I get this right at the deployment stage with epinio Deploying application ... ❌ error pushing app to server: can't deploy app: Internal Server Error: failed to fetch https://github.com/epinio/helm-charts/releases/download/epinio-application-0.1.18/epinio-application-0.1.18.tgz : 401 Unauthorized

Hello All 👋 I am trying out Epinio for my COmpany’s local development environment. I need help with configuring the Epinio setup into my Local Rancher Desktop. I have followed the steps mentioned in the Docs. However, when I am accessing https://epinio.127.0.0.1.sslip.io I get certificate error in my Chrome. I can see all my services up and running, can you help me with this so that we in our company can start using Epinio ? Thanks in advance !

❯ kubectl get pods -A
NAMESPACE      NAME                                       READY   STATUS      RESTARTS      AGE
kube-system    helm-install-traefik-crd-zrptx             0/1     Completed   0             29m
kube-system    helm-install-traefik-z7hb7                 0/1     Completed   2             29m
kube-system    local-path-provisioner-6c79684f77-qgddd    1/1     Running     1 (18m ago)   29m
kube-system    svclb-traefik-5rxc4                        2/2     Running     2 (18m ago)   29m
cert-manager   cert-manager-cainjector-747cfdfd87-9ghhb   1/1     Running     1 (18m ago)   28m
cert-manager   cert-manager-webhook-67cb765ff6-wr5mb      1/1     Running     1 (18m ago)   28m
epinio         minio-0                                    1/1     Running     1 (18m ago)   27m
kube-system    coredns-d76bd69b-mmfbp                     1/1     Running     1 (18m ago)   29m
cert-manager   cert-manager-5b6d4f8d44-7kf49              1/1     Running     1 (18m ago)   28m
epinio         epinio-server-997c96b44-8pmgs              1/1     Running     1 (18m ago)   27m
epinio         kubed-7d7cb55879-hfcqt                     1/1     Running     1 (18m ago)   27m
epinio         epinio-ui-6958cf6685-btzwk                 1/1     Running     1 (18m ago)   27m
epinio         registry-55bc9c864b-2ddk7                  2/2     Running     2 (18m ago)   27m
kube-system    traefik-df4ff85d6-qnc47                    1/1     Running     1 (18m ago)   29m
kube-system    metrics-server-7cd5fcb6b7-522vz            1/1     Running     1 (18m ago)   29m

Trying Epinio Extension on Docker Desktop Windows 11 with WSL - I have kubernetes installed and running. The extension installed successfully but when trying to install Epinio binaries (Install Button in the extension UI) Getting the following error - What does that mean? and how to get a running Epinio on Windows?

Hello everyone, my name is David Vollath and I'm studying computer science at the Nuremberg Institute of Technology. I'm currently writing (or rather beginning to write) my bachelor's thesis about adding multi-cluster support to epinio. I hope to get help if needed and eventually feedback once my work has progressed far enough for that. Cheers, David

Looks like a start-up from Rancher roots trying to address the same problem https://www.itprotoday.com/containers/acorn-labs-rancher-co-founders-new-kubernetes-startup

BTW, anybody here who needs help with getting epinio into AWS with ALB + WAF, let me know... with the help of @cuddly-holiday-9089, we made good progress and should be able to write a good instruction set in the community documentation.

just as a workaround, does it work with the

--skip-ssl-verification

flag?

any consideration for this 😉 https://github.com/epinio/epinio/issues/1681

Hi @strong-glass-25362 I was looking on how to send you an invitation when I noticed you managed to join already, so welcome ! After creating the services, the command you want to run in order to "bind" it to the application is

epinio service bind

but this assumes the application is already created. The

-b

flag of the

push

command is there to bind existing configurations but the service configurations are only created the first time the service is bound to an application. So there is a chicken-egg problem here. The solution I think is: •

epinio service create...

•

epinio app create...

(beware, this is "create" not "push") •

epinio service bind

(now the application exists, so this is possible) •

epinio push

let me give it a try myself to save some back an forth between timezones if this doesn't work.

hi all, tomorrow we are going to have an online meetup about Epinio! Join us to see a demo, and ask any questions about it! https://more.suse.com/global_online_meetup_epinio_developer_platform.html 🚀 :epinio:

Who here made it to our Epinio Global Online meetup this week?

@busy-teacher-96897 this is how I usually setup my development environment (moving our conversation here):

#!/bin/bash

# Checkout a branch
git checkout 1571-re-dex-spike

# Sync git submodule
# NOTE: This will cleanup dangling files inside the submodule too (because of `git clean -dffx`).
# Adapt this command if necessary
git submodule sync --recursive && git submodule update --init --recursive && git submodule foreach --recursive "git co . && git reset --hard && git clean -dffx"

# Prepare a dev cluster
make acceptance-cluster-setup

# Configure KUBECONFIG to talk to the dev cluster
export KUBECONFIG=$PWD/tmp/acceptance-kubeconfig

# Install cert-manager
make install-cert-manager

# Install Epinio from the checked out commit
make prepare_environmnet_k3d

# You should now be able to use Epinio

I was talking with @busy-teacher-96897 and we think it may be useful to have a

community

repository in Epinio where people can contribute their scripts or other tooling around Epinio. We can start with a README that explains what's in each directory and each directory (tool/script/whatever) can have its own README. If a tool becomes popular it could be extracted to its own repo but for now, keeping them in one place should be a good start. What do you all think? Fred already has some useful Makefiles and scripts to help deploy Epinio in AWS.

@broad-dream-81849 do you have any docs around the test you did with dex and GitHub connector? @busy-teacher-96897 might find it useful

yeah, thanks!

not really, because it was something more Dex/Github related, and they provide their docs around it. But I can help you on this 🙂 Maybe we could think about adding this as a tutorial/how-to/example if it's useful. After have installed Epinio you need to create a Github application, so go to your Profile > Developer Settings > Oauth Apps > New Oauth App. Name: "Whatever", Homepage: "https://auth.myepiniocluster.com", Authorization callback URL: "https://auth.myepiniocluster.com/callback" (probably for the homepage you can define the "epinio.xxxx.yy" or something else). Then take note of the ClientID and the ClientSecret. With those you need to edit the

config.yaml

inside the

dex-config

secret in the

epinio

namespace, adding a Github connector:

connectors:
- type: github
    id: github
    name: GitHub
    config:
    clientID: my-client-id
    clientSecret: my-secret
    redirectURI: "<https://auth.myepiniocluster.com/callback>"

Then you can restart Dex to get the configuration, and you are good to go! You can probably tweak also the helm-chart values to push the dex configuration instead of manually update them, but I haven't tried it.

btw, Epinio version

1.3.0

is now released: https://github.com/epinio/epinio/releases/tag/v1.3.0 including external authentication with dex, self-updating cli and other improvements and fixes. Everybody's feedback is welcome!

Epinio is discussed between 38:20 & 42:35