k8s-specs's People
Forkers
mario21ic patrickleet netcsc abechin preetampvp sripoojitha kilroy396 gmlp vimalkrishna rogervaas haani-niyaz joostvdg enixdark bouchas jkrishnarao jhagege bharu456 omjsr pravasna prasantk direkshan-digital asidhu11702 stubrowncloudbees quietcoolwu po-- zeroc0d3lab prageethw sabya1981 nnrgithub solidnerd nguyenhoangnhon jgoodw1n tgilkerson raghuk134 docker-flow pkvanda j4ckzh0u plusx2012 ytra-cloud changqings devops165 diegopacheco michaelpetik-axcelinno shanmukhavardhan rjudin hoaitang rav121 dinovoh gouthamchilakala hien dmilan77 vamsikukati mikebell90 ammarqq lchennup edcelvista bnivasreddy rm3l naveen7669 hayari iamjeerge dlaban kyanite futuoleng warrenv odusseos2017 wasifibrahim29 dieple benjamin-bissett-reisys darinpope nk-gears medhir premgurung vignesh-v-nutanix k-groshev w00jay ozbillwang blairham sameer-io mamtasmi claudiutraistaru-cluttered boriphuth sudhakarvp phusdu nickcschneider anilkumarkoduri anil-mirge oyekunle-mark nickherron101 rajkumar456 gopishravs chenjianagain vamsikrishnakukati sharpsound sharonsahadevan playhing sampadrout naveenkumarboopathi fred070 223kazukik8s-specs's Issues
Educative.io Course on Advanced Monitoring / Logging
Recently signed up for the Advanced Kubernetes Techniques: Monitoring, Logging, Auto-Scaling course with educative.io and so far really liking the walk through of how to configure more detailed metrics and logging tools. Have ran into a couple of issues so far and just wanted to let you know they are out there.
- When you are running a local kube cluster, regardless of if I used it with k3s, microk8s, or kubeadm, with a non-public cluster, or with a cluster that is using a self-signed cert (like when deploying with KubeSpray), the metrics-server fails to setup. The issue is in metrics-server itself as it expects that the certs be issued by a valid CA. Adding the --kubelet-insecure-tls flag fixes the issue and is explored here, but took a minute to find and would be confusing for anyone not running on a public cluster. Link to issue where the flag is explained and a walk through to setup certs that will work here.
- For the next section on Horizontal Auto-Scaling, the first example of the go-demo app (go-demo-5-no-sidecar-mem.yml) fails to setup on a local cluster. The error thrown in logs is:
goroutine 1 [running]:
main.setupDb()
/home/jenkins/workspace/go-demo-5_master-PUGTP37ZPAXQ7QFVCZOSPGHDUP64R2OHAFU6ZBGYY43JK5YVI5GA/main.go:68 +0x2b4
main.main()
/home/jenkins/workspace/go-demo-5_master-PUGTP37ZPAXQ7QFVCZOSPGHDUP64R2OHAFU6ZBGYY43JK5YVI5GA/main.go:47 +0x49
Even with the above still really enjoying things and hope to get through the rest of the course soon.
Curl command times out on page 29
I am trying the lesson "Creating Ingress Resources Based On Paths" and am on page 29. The curl command (curl -i "http://$IP/demo/hello") just times out. I have confirmed all is up and $IP is set with an ip address. I also confirmed that the "ingress" addon is enabled.
I have done a minikube delete twice now and copy/pasted the code. All works right up to this curl command which takes forever and just returns this finally...
$ minikube addons list|grep ingress
ingress: enabled
$ IP=$(kubectl get ingress go-demo-2
-o jsonpath="{.status.loadBalancer.ingress[0].ip}")
$ echo $IP
10.0.2.15
$ curl -i "http://$IP/demo/hello"
curl: (7) Failed to connect to 10.0.2.15 port 80: Connection timed out
I have pulled the latest changes as well...
$ git pull
Already up to date.
Outdated Ingress configuration
All of the Ingress
objects are using outdated syntax that doesn't work with the latest version of kube at the time of this writing.
In particular, the following changes need to be made to all Ingress
object configs:
- the value of
apiVersion
should be changed tonetworking.k8s.io/v1
pathType
is now required next topath
serviceName
andservicePort
are deprecated and should instead be replaced w/ something like this:
service:
name: foo
port:
number: 8080
Educative.io course issue : A Practical Guide to Kubernetes
I am facing error in step https://www.educative.io/courses/practical-guide-to-kubernetes/3jpxwq1OYEM. It is at section Accessing the Cluster: Adding the Load Balancer
I do
kubectl create
-f https://raw.githubusercontent.com/kubernetes/kops/master/addons/ingress-nginx/v1.6.0.yaml
But I am getting error. I have downloaded v1.6.0 and replaced "rbac.authorization.k8s.io/v1beta1" with "rbac.authorization.k8s.io/v1" and run local yaml file with create command. It is giving error:
Warning Unhealthy 2s (x5 over 20s) kubelet Readiness probe failed: Get "http://100.96.4.20:10254/healthz": dial tcp 100.96.4.20:8080: connect: connection refused
Is it because port 10254 not open?
Can you help me?
Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions
Got following errors while trying some of the jenkins deployments:
$ kubectl logs jenkins-6d778c8bc9-s22v6 -p
touch: cannot touch '/var/jenkins_home/copy_reference_file.log': Permission denied
Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions?
After some searching, found that the errors were gone after adding following under specs:
securityContext:
fsGroup: 1000
runAsUser: 0
Version:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:53:20Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
go-demo-2-rs.yml is not creating cluster
Step to reproduce
git pull
minikube start --vm-driver=virtualbox
kubectl config current-context
cat svc/go-demo-2-rs.yml
kubectl create -f svc/go-demo-2-rs.yml
kubectl get -f svc/go-demo-2-rs.yml
replicas never get into READY state.
NAME DESIRED CURRENT READY AGE
go-demo-2 2 2 0 1m
Dependency Dashboard
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Warning
Renovate failed to look up the following dependencies: Failed to look up helm package exposecontroller
, Failed to look up helm package jenkins
.
Files affected: charts/preview/requirements.yaml
, helm/jenkins/requirements.yaml
, helm/jenkins2/requirements.yaml
This repository currently has no open or pending branches.
Detected dependencies
helm-requirements
charts/maesh/requirements.yaml
charts/preview/requirements.yaml
exposecontroller 2.3.56
exposecontroller 2.3.56
helm/jenkins/requirements.yaml
jenkins 1.5.0
helm/jenkins2/requirements.yaml
jenkins 1.5.0
helm-values
charts/k8s-specs/values.yaml
charts/preview/values.yaml
terraform
terraform/config.tf
terraform/doks/cluster.tf
terraform/gke-crossplane/cluster.tf
terraform/gke-jx/cluster.tf
terraform/gke/cluster.tf
- Check this box to trigger a request for Renovate to run again on this repository
Please add a note about addons staying enabled
It might be worth a note that when you enable addons, they remain enabled even after you do a minikube delete. It is not at first expected because we are working with minikube. It is easy to get lost and forget that kubectl is local and not in the vm destroyed by "minikube delete".
I only mention this because as someone new to minikube/kubernetes I followed the instructions on page 127 ("minikube addons enable ingress"). All worked as expected but then had to restart these lessons for an unrelated reason. When I got to the "curl" steps just previous to enabling the ingress addon I was expecting a "Connection refused" as seen on page 125/126 (because the book expects it to be disabled) and I was getting 200s. This was confusing at first and caused me to restart the lesson a couple of times until I figured out the issue (or rather what I was missing). A note on this around where you enable the addon on page 127 would have made me expect the 200s and I would have moved on.
Port number on Service definition
k8s-specs/deploy/go-demo-2-scaled.yml
Line 23 in e94b4a8
Hello
I'm reading your DevOps 2.3 toolkit book and I came across this Deployment definition.
I was wondering, shouldn't the Deployment port be 27017
since the corresponding Service declares:
spec:
ports:
- port: 27017
?
Thank you
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.