Interestingly I may be seeing a similar problem in my Free space.
So I tried emptying my space of and everything that I could. Verified that no pods are running that I can see in my space.
I tried running kubernetes describe quota to see my usage and it still saying that i am using cpu on limit and requests. Not sure if that is suppose to happen or not.
K8s experts what you think?
$ kubectl describe quota
Name: 8mobius8-quota
Namespace: 8mobius8
Resource Used Hard
-------- ---- ----
count/certificates 0 10
count/configmaps 0 50
count/cronjobs.batch 0 10
count/daemonsets 0 0
count/deployments.apps 3 10
count/deployments.extensions 0 10
count/ingresses 0 10
count/jobs.batch 0 10
count/persistentvolumeclaims 0 10
count/pods 1 10
count/replicasets 0 20
count/replicationcontrollers 0 10
count/secrets 5 25
count/services 0 20
count/services.loadbalancers 0 0
count/services.nodeports 0 10
count/statefulsets.apps 0 5
limits.cpu 1 1
limits.ephemeral-storage 0 1Gi
limits.memory 100Mi 512Mi
requests.cpu 20m 20m
requests.memory 100Mi 512Mi
requests.storage 0 100Mi
but same here my describe quota return 10 pods while get pods return no resources
still
Hello everyone - things should be repaired - ideally your pods have been online off and on during all this hassle. I've verified everyone who posted here last night has their pods up and running.. Been a crazy 24 hours - our master servers came under very heavy attack.. We're looking at our options for providing a reliable hosting service - unfortunately the free tier is becoming extremely hard to defend. We'll follow up on this in the next couple days... Rest assured paying users: things should only get more reliable going forward :)
I'm going to take a very very very needed nap, but please feel free to ping here if you're having an issues, and I'd be happy to take a look!
The resource quota issue should also be resolved now - this was also due to the master servers being under tremendous load. Thanks for your patience everyone!
@carljmosca Seandon was the one who fixed, but I can try and explain: AWS unexpectedly terminated two of our masters (out of 3 total) for our USW1 cluster. When we spun them back up, the certs we generated were invalid (our mistake was that Kube requires masters to all have the exact same certificates, rather than just ones signed by the same CA). This caused the ectd database on the 2 new masters to fall behind, and therefore everyone's resource quota (stored on etcd) was out of sync, so the workers to not be able to schedule any new pods (also exacerbated by the cert issue when talking to the masters). Fixing those certs and rebooting the masters fixed the cluster and allowed pods to be scheduled again.
apologies for the outage!
weve been thinking about this - are considering allowing dedicated IPs for paying customers
Hey there! Ran into a tiny problem with my free tier 'repo' setup on Kubesail.com: Looks like the 'repo' functionality actually builds the image in the kubesail's private registry but my pods can't start due to a Unauthorized error when trying to get the image to run. Is the private registry accessible for free tier accounts?
The build seems to show as passing on the UI, however when I look at the pods I see a pull image error:
failed to resolve reference "registry.kubesail.com/....
failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
Ill take a look - perhaps the Deployment had the imagePullSecret removed or our system failed to patch it on correctly...
4 replies
we need some better docs around that feature!
@progressbarteam yes that was a node IP - unfortunatly this weekend we had a bit of an issue which moved lots of pods onto new nodes. Were working on a better solution - and you should be able to use
ext-a.kubesail.io Instead of any IP
but thats a bit of a beta system - let me know if it works for you :)
@erulabs is there possibly something with the new setup you can think of that would cause my pods to crash while trying to download files? I can connect to the pod for a few seconds through the kubesail site but then they stop responding and crash right after logging out the init of the first download.
Typically an issue with our infrastructure would prevent pods from starting at all - they wouldnt effect what goes on once they launch
I do have one question though. I can only join on the Node port, but to be able to allow people to join from the public list, it has to be available on 34197 UDP. Is there something I can do to correct that?
im actually tempted to patch it - factorio is brilliant but i dont think the developers do much devops :P
i believe the problem is that factorio tries to determine its public IP - since its inside a container it doesnt guess right :(
but “bind” is a bad name - we dont want to bind a specific address - we just want to advertise a specific address
it should have an —advertise-address, but if i recall last time i looked it did not :(
I'm actually running into some UX issues with the site and managing environment variables. On FF once I create a variable, I cannot delete it. Clicking the 'x' to remove the variable once seems to shift the page slightly. A second time deletes the variable from the list, but when I click save, it comes right back with it's old value.