huib-portainer

You could try removing the global mode from the yaml and switching the network from overlay to bridge. But I haven't tried that myself.

Please have a look at the documentation: https://docs.portainer.io/v/ce-2.9/admin/environments/add/api And for more details on the API see: https://app.swaggerhub.com/apis/portainer/portainer-ce/2.9.2#/endpoints/EndpointCreate Or use this example as a starting point: ``` curl --request POST --insecure...

Could there be an issue with your overlay network?

Are you running the Agent globally? ``` deploy: mode: global placement: constraints: [node.platform.os == linux] ``` Which is different from Portainer, which will be running on the manager node: ```...

Hi, that might actually be solved in one of our preview versions. Please give it a try by using the images `portainerci/agent:kubernetes-edge-stacks` and `portainerci/portainer:pr5276` and let us know how it's...

I wouldn't recommend exposing Portainer directly to the internet. And even with HTTPS now being enabled by default, sending your credentials with every request isn't really best practise. Maybe consider...

>why the writers of Portainer decided to remove the --no-auth Because Portainer provides access to your deployment environment, it does need to provide a basic level of security. It would...

Did the 2.15 release solve this issue?

I use the logout url `https://huib-portainer.au.auth0.com/v2/logout?client_id=6BJJNg...HR0A3R&returnTo=https://192.168.189.128:9443` When logging out or navigating to `https://192.168.189.128:9443` I end up at `https://192.168.189.128:9443/#!/auth` which allows me to log back in. And after logging in I...

Thank you for asking that question. What would you perceive to be a viable alternative? Of course moving to manifests is always an option. But other recent projects, like Acorn,...