Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Dan Pastusek
    @PastuDan
    kubectl describe nodes
    cpu 1877m (93%) 3227m (161%)
    you're actually at 1877m CPU requested, so your pod with 125m would put it over 2 cpu (2000m)
    keep in mind that other system services operate on this node (kube-proxy, dns, cert-manager, etc) and take up a small amount of CPU
    its ok for the total CPU limits to be higher than 2000m, but CPU requests are guaranteed, so must not exceed 2000m
    I'd recommend lowering the limits slightly on all your pods. 100m should be fine for everything. Limits are more critical. Setting those to 500 or 1000m allows those apps to burst when needed.
    DavidCamelo
    @DavidCamelo
    image.png
    Got it
    Dan Pastusek
    @PastuDan
    Oh sorry! That error will come up if you try using kubectl through the agent. The config page mentions: "You may also need to use kubectl --insecure-skip-tls-verify=true until you configure your Kubernetes Cluster with your KubeSail hostname."
    The alternative is I can give you the config file for your cluster to manage it directly. I'll send you that via email.
    DavidCamelo
    @DavidCamelo
    Thanks!
    firewall.gif
    DavidCamelo
    @DavidCamelo
    image.png
    @PastuDan SSL certificates were never generated, I worry that in the future the certificates of other sites will expire and it seems that the generation is not working
    DavidCamelo
    @DavidCamelo
    Hello @PastuDan, Any updates on SSL certificates?
    DavidCamelo
    @DavidCamelo
    image.png
    another thing. I can't make backups in the dedicated cluster
    calebcoverdale
    @calebcoverdale
    CleanShot 2020-10-28 at 15-12-27@2x.png
    I am trying to get setup, I added the config to my cluster, but when I try accessing the website it gives this error
    calebcoverdale
    @calebcoverdale
    Is there an easy way to clear all configs with my KubeSail account and start fresh?
    calebcoverdale
    @calebcoverdale
    Looks like I can't do anything with KubeSail - anyone recommend any alternatives?
    Seandon Mooy
    @erulabs
    Hey @calebcoverdale - Sorry for the slow reply - we're working on resolving that error for you now!
    Seandon Mooy
    @erulabs
    Is it possible you could share a bit more about your browser version and O/S?
    calebcoverdale
    @calebcoverdale
    macOS Edge/Chrome/Safari
    Haven't tested it yet on Windows.
    "Cannot read property 'namespaces' of undefined." same issue on Windows Edge.
    Edge v 86.0.622.56
    Safari v 14
    Seandon Mooy
    @erulabs
    Thank you! Certainly appears to be a bug on our side - we should have a fix out for you shortly :)
    calebcoverdale
    @calebcoverdale
    Thanks! You da bomb.
    Dan Pastusek
    @PastuDan
    @DavidCamelo it is strange that those certs never went valid. It seems that there are 2 problems. The kubesail-letsencrypt clusterissuer got deleted, but also those 2 ingresses are referencing a cluster issuer named simply letscencrypt
    I'll recreate the kubesail-letsencrypt clusterissuer, and then update those ingresses to reference it
    Seandon Mooy
    @erulabs
    @calebcoverdale - I believe we've found the issue - should have a patch out for you within the next hour or so! Thanks for reporting that issue!
    DavidCamelo
    @DavidCamelo
    @PastuDan thanks
    calebcoverdale
    @calebcoverdale
    Incredible. thanks @erulabs
    Dan Pastusek
    @PastuDan
    @DavidCamelo fixed your ingresses & certs.. all should be healthy now!
    DavidCamelo
    @DavidCamelo
    Looks good, tahnks!
    Dan Pastusek
    @PastuDan
    Can you also test backups now? I increased your quota
    DavidCamelo
    @DavidCamelo
    I'll check
    Dan Pastusek
    @PastuDan
    That was a hold-over from when you transfered your cluster to your ownership
    I never re-upped the quota
    calebcoverdale
    @calebcoverdale
    I got logged in! Thanks guys.
    DavidCamelo
    @DavidCamelo
    @PastuDan The backup job never was triggered :(
    image.png
    Dan Pastusek
    @PastuDan
    It looks like your cluster is on a newer version of kubernetes than what our backup system currently supports. We are rolling out a fix now.. hold tight! :)
    DavidCamelo
    @DavidCamelo
    got it, thanks !
    Dan Pastusek
    @PastuDan
    @DavidCamelo the backup script is now fixed. One more try please :)
    DavidCamelo
    @DavidCamelo
    On my way
    Dan Pastusek
    @PastuDan
    Awesome thank you
    DavidCamelo
    @DavidCamelo
    image.png