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

HI @cuddly-holiday-9089 @broad-dream-81849 Not sure if this is really a bug on dex, but here u go: https://github.com/epinio/epinio/issues/1781

Epinio is now available from the Civo Marketplace https://twitter.com/CivoCloud/status/1582008344004288512 https://www.civo.com/marketplace/Epinio

please like this tweet if you like epinio :D

Interesting read: https://thenewstack.io/what-we-learned-from-enabling-developer-self-service/

Good article!

Hi guys, I tried to push my local image with epinio. It show that kubelet can not pull image because it can’t find in docker.io registry. Does anyone know what is the cause of this problem ? Is it because I’m using Apple silicon while my image is Amd64 ? (Docker has this same issue i think) I’m using epinio push --container-image-url <my-image> as a push command.

With simple example projects e.g. paketo/samples epinio works wonderfully. When I go to my own projects the issues I have are build issues. Like this. Where do you recommend learning more about dealing with these issues?

Hi everyone, I just installed epinio on minikube using Helm in my macbook (M1)

helm install epinio --create-namespace --namespace epinio epinio/epinio --set global.domain=<http://192.168.49.2.sslip.io|192.168.49.2.sslip.io>

After doing a

minikube service -n epinio epinio-ui --url

, I’m able to access the Epinio UI via

<http://127.0.0.1:63777>

but the

admin/password

login is not working (see screenshot). Anyone know why? 🤔 Thanks in advance

While I like the pack builds is there a way to also bypass the build portion of epinio and use my own build if I want too?

It's the easiest way to begin moving legacy code into epinio

And I do test before hand to see if that app is available using a curl command

Part of testing this out for legacy apps is trying to see if I can export the helm chart so that I can move this from a dev to deploy scenario in CI

Hi @freezing-holiday-13112, could you export an higher

TRACE_LEVEL

env var to get some logs? In your shell for the cli, and in the epinio deployment for the server

Is there a way to have epinio just do a build?

ll