by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Seandon Mooy
    @erulabs
    -p 8080:80 implies they're forwarding port 8080 on their machine to port 80 inside the container. So for kubernetes/phpmyadmin, you'll want to use port 80.
    In any case, let me know when you swap the image back to phpmyadmin, and I can take a closer look :)
    DavidCamelo
    @DavidCamelo
    phpmyadmin_local.gif
    You're right, I tested locally and the container runs in port 80 internally and exposes it in port 8080
    I just change the image to phpmyadmin in kubernetes
    Seandon Mooy
    @erulabs
    Hi @DavidCamelo it seems to me that the phpmyadmin container just isn't listening on any ports! One trick is to use kubectl exec (or click on the pod in our UI) and log into the container. There you could try curl localhost, and see that it's not working! :(
    My guess is something is preventing phpmyadmin from starting - maybe a misconfiguration?
    Since you're getting it working locally, my guess is its the PMA_HOST environment variable you're using, but it's hard to say. Perhaps there is a debug mode you could enable? I don't know much about phpmyadmin, sorry :(
    DavidCamelo
    @DavidCamelo
    don't worry, I'll keep researching until it works, thank you very much for your tips.
    image.png
    DavidCamelo
    @DavidCamelo
    image.png
    looks like the apache2 inside the container is stopped, I ran service apache2 start and now is working
    image.png
    really very strange, I will continue to look into it, again thank you very much!
    DavidCamelo
    @DavidCamelo
    Hi @erulabs FYI I just created an issue in phpmyadmin github project in case you want to follow phpmyadmin/docker#294
    Seandon Mooy
    @erulabs
    Oh cool! Thanks for battling that one! It seems like some sort of issue with how the container starts up - strange its not bringing up apache! If I get some free time I might try to fix that later!
    Stanley Nguyen
    @stanleynguyen
    hey @erulabs my DNS issue's happening again. I think this triggers whenever I do a rollout restart deployment/. There were some successful ones long ago though. But this DNS issue has been happening for the last couple of rollout restarts
    Seandon Mooy
    @erulabs
    Ack - will look @stanleynguyen - thanks for the heads up...
    Juuso Laine
    @jusola
    Not sure if this is related to the DNS issues mentioned by Stanley Nguyen, but I can't connect anywhere from pods in kubesail. I cannot connect to any other pods within the cluster or to anywhere else on the internet. The same configuration works locally on my machine though. I had one pod that had internet connection but after restarting it with 'rollout restart deployment', it couldn't connect anymore.
    Juuso Laine
    @jusola
    It seems that the network starts working somewhere between 30 minutes and a couple hours after pod restart
    Seandon Mooy
    @erulabs
    Hello everyone - we're experiencing a major outage in our US West 1 cluster. It appears to be due to our cloud provider. We're working on resolving it asap!!!
    Seandon Mooy
    @erulabs
    Okay, a good chuck of our hosts are back online - so far I believe there was a networking hiccup, but our system did not weather it. Working on it!! Thanks for your patience everyone!
    Seandon Mooy
    @erulabs
    Most of the issues should now be resolved - although there is an ongoing issue with creating new Volumes in US West 1.
    Seandon Mooy
    @erulabs
    Hello everyone - the volume creation issues have been resolved in US West 1 but we're still seeing some networking issues, although they should be fairly rare and random. We should have this solved shortly! Thanks for your patience everyone!
    Seandon Mooy
    @erulabs
    Phew, okay - after almost 24 hours of debugging I believe we've ironed out the issues. Please let me know if you spot any networking strangeness! Also, if you'd like your own private cluster, or if you need a hand running a cluster with >10000 services, let us know!
    Seandon Mooy
    @erulabs
    The final TLDR on the networking issues is that it turns out we were not restricting in all cases how users could trigger pods to be spawned. A very clever user figured out how to spawn 30k jobs that clogged our system something awful :( We've put some limits in place to prevent this from happening again, as well as major optimizations to the clusters. Once again I apologize if you noticed any outages or issues - please let us know if we can do anything to help
    irideakatsuki
    @irideakatsuki
    Hello, I want to ask something. Is there any bandwidth limit for free tier?
    DavidCamelo
    @DavidCamelo
    Hi @erulabs I'm trying to increase the max upload size for my Wordpress deployment, I need to modify nginx.ingress.kubernetes.io/proxy-body-size to 256m but when I try to do this it always overwrites it by 10m
    proxy-body-size.gif
    Seandon Mooy
    @erulabs
    Hi @DavidCamelo - that limit is in place to prevent abuse on the free tier but I will increase it for paid users :) Do you specifically need 256m? I'll see what I can do about that!
    DavidCamelo
    @DavidCamelo
    @erulabs Yes, 256m is enough for me
    Seandon Mooy
    @erulabs
    Hey @DavidCamelo We've gone ahead and raised to limit to 256m for paying users! Thanks for asking - that's a good improvement (that limit was too low previously!). Let us know if we can do anything else to help!
    DavidCamelo
    @DavidCamelo
    For now, that's all, I love that every day kubesail keeps getting better, thanks!
    Alexander Kucherov
    @alexander-kucherov
    Hello! I'm trying to validate domain. I've already added DNS TXT records. Verifying. 311 attempts... and dont't increase. Domain kucherov.tk
    Dan Pastusek
    @PastuDan
    @alexander-kucherov I see from my end that the TXT record is correct on your domain.. would you mind reloading the page and clicking the "Verify DNS Record" button again?
    Its possible that our DNS system cached the result prior to it being added
    Alexander Kucherov
    @alexander-kucherov
    @PastuDan Yes. I've already clicked Verify button. It seems like cached
    DavidCamelo
    @DavidCamelo
    Hi @erulabs, again me asking questions 😳
    Is there a way to create a single TLS certificate for all subdomains and not have a certificate for each subdomain?
    Something like:
    cert-manager.io/alt-names: "*.davidcamelo.com" cert-manager.io/common-name: "*.davidcamelo.com"
    Dan Pastusek
    @PastuDan
    @alexander-kucherov I went ahead and verified your domain for you. Its not clear why the automated system isn't working, I need to dig further and will update chat once I find anything. Please let me know if you have any issues with other domains!
    Dan Pastusek
    @PastuDan
    @DavidCamelo looks like, at a high level, our ClusterIssuer would need to support the DNS solver in order to enable wildcard certificates. (https://cert-manager.io/docs/configuration/acme/#adding-multiple-solver-types). Right now we only have the HTTP solver enabled for our ClusterIssuer. I'll double check with @erulabs, but it seems very possible that we can enable that for you.
    DavidCamelo
    @DavidCamelo
    @PastuDan That sounds great!
    Dan Pastusek
    @PastuDan
    Hey @DavidCamelo, I did a bit of digging, and adding DNS support is a bit more complex than I initially thought. The issue is that, because cert-manager is non-interactive, you yourself need to generate the the token that Lets Encrypt verifies, set the DNS record, and then generate the certificate request (https://cert-manager.io/docs/configuration/acme/dns01/acme-dns/ -> JSON credentials). We can make a UI to help do this, but that will have to be further down on our roadmap.
    In the meantime, you could use certbot to generate the wildcard cert yourself, and then upload it to a Secret in KubeSail. Please do let me know if you run into issues / limits generating certificates for each hostname... Lets Encrypt is very generous with their limits and you shouldn't hit them under normal usage.
    DavidCamelo
    @DavidCamelo
    Hi @PastuDan, there is no problem generating the certificates, I was just asking because I thought it would be more convenient to have a single certificate for each domain and all subdomains, for example I have these two certificates for a single wordpress deploy: www.davidcamelo.com which redirects to davidcamelo.com
    image.png
    Seandon Mooy
    @erulabs
    Hey @DavidCamelo - That does happen currently - we're planning on having our system automatically bundle certificates but the problem is it would be hard to know if one day you wanted that cert to be separate... Gets kind of tricky :) Rest assured the certificates will auto-renew automatically, so hopefully it's not much of a hassle how is it!
    You can probably generate your own Certificate object manually (https://cert-manager.io/docs/concepts/certificate/) and get what you want, but our UI will create one certificate per hostname
    DavidCamelo
    @DavidCamelo
    Got it. Thanks for your help and explanation. I'll keep that in mind.
    DavidCamelo
    @DavidCamelo
    Hi @erulabs @PastuDan, is there a way to download the invoice for kubesail's monthly payment?
    Seandon Mooy
    @erulabs
    Hey @DavidCamelo - We can send you an invoice but unfortunately no view for that on the site just yet :(