Comments (11)
Also, we've distributed our images across all AWS regions so you can now run in us-central-1.
from kip.
Thanks a lot for trying kip, @joh4n !
First I add the aws credentials in deploy/manifests/kip/base/provider.yaml
If you want to use kip on minikube, kustomize scrips in https://github.com/elotl/kip/blob/master/deploy/manifests/kip/overlays/minikube/
are a better choice. Can you please retry with manifests in this directory? If you still do not see kip node, kubectl -n kube-system get pods
should show *kip*
pod. Can you please share kubectl logs
from kip pod? Thanks!
from kip.
One other note: We updated the name of the kip pod to kip-provider-0
and missed updating the references in the README and troubleshooting doc. Apologies!
As @myechuri pointed out, you'll want to give the minikube manifests a shot. Minikube is a bit of a different setup for kip and you'll need to configure a couple additional items to make kip work (check out the instructions here: https://github.com/elotl/kip/blob/master/deploy/manifests/kip/overlays/minikube/kustomization.yaml#L1-L26):
- Credentials for starting instances in AWS since kip can't use an instance profile if its running on a laptop. The credentials can be specified using a secret or directly into provider.yaml (but a secret is preferred).
- You'll need to tell kip where it should launch instances (what VPC & subnet) in provider.yaml
- You'll need to create an additional security group that kip can use to connect to instances it creates. That security group should, at a minimum, open TCP port 6421 to traffic from your laptop. That security group needs to be manually specified in provider.yaml as well: https://github.com/elotl/kip/blob/master/deploy/manifests/kip/overlays/minikube/provider.yaml#L27-L29
Feel free to comment here if things are unclear or if you run into issues.
from kip.
I missed the minikube folder thx. However, I followed the instructions in: https://github.com/elotl/kip/blob/master/deploy/manifests/kip/overlays/minikube/kustomization.yaml#L1-L26
with provider.yaml
apiVersion: v1
cloud:
aws:
# You can also use environment variables for region, access and secret key.
region: eu-central-1
accessKeyID: ""
secretAccessKey: ""
vpcID: vpc-0eddxxxxxxxxxxx
subnetID: subnet-0eexxxxxxxx
etcd:
internal:
dataDir: /opt/kip/data
cells:
standbyCells:
defaultInstanceType: t3.nano
defaultVolumeSize: 15G
bootImageSpec:
owners: 689494258501
filters: name=elotl-kip-*
nametag: minikube
itzo:
url: https://itzo-kip-download.s3.amazonaws.com
version: latest
# Optional, if kip needs to connect to cells via public IPs.
# extraCIDRs:
# - FILL_IN
extraSecurityGroups:
- sg-0bf4xxxxxxx
kubelet:
cpu: "100"
memory: "512Gi"
pods: "200"
and kustomization.yaml
bases:
- ../minikube
namespace: kube-system
configMapGenerator:
- name: kip-config
behavior: merge
files:
- provider.yaml
secretGenerator:
- name: kip-secrets
literals:
- AWS_ACCESS_KEY_ID=AKIxxxxxxxxx
- AWS_SECRET_ACCESS_KEY=1lXxxxxxxxxxxxxxxxxx
with that kustomiztion.yaml I get the error
Error: merging from generator &{0xc0007f6120 { } {{ kip-config merge {[] [provider.yaml] []} <nil>}}}: id resid.ResId{Gvk:resid.Gvk{Group:"", Version:"v1", Kind:"ConfigMap"}, Name:"kip-config", Namespace:""} does not exist; cannot merge or replace
error: no objects passed to apply
so I updated it with
.
.
configMapGenerator:
- name: config
behavior: merge
.
.
.
that runs but I get the error:
kubectl -n kube-system logs kip-provider-0
error: a container name must be specified for pod kip-provider-0, choose one of: [kip kube-proxy] or one of the init containers: [init-cert]
from kip.
Hi @joh4n ,
kubectl -n kube-system logs kip-provider-0
error: a container name must be specified for pod kip-provider-0, choose one of: [kip kube-proxy] or one of the init containers: [init-cert]
Can you please run kubectl logs -n kube-system kip-provider-0 kip
? kip-provider-0
is a pod with kip
container in it, and we would be interested in logs from kip
container.
Also, can you please confirm if you see kip-provider-0
in the output of kubectl get nodes
? Thanks.
from kip.
region: eu-central-1
@joh4n : kip trial is currently setup for us-east-1
region . Apologies for not calling this out in the readme, we will update readme. Can you please try us-east-1
? Thanks.
from kip.
This is with us-east-1 as a region.
(ignore fatal: ref HEAD is not a symbolic ref
it is a set up issue in my zsh when I check out a tag and I have been to lazy to fix it)
from kip.
@joh4n : let me repeat your steps with your your kustomization.yaml
and see if i can reproduce your error. Will update by the end of the day.
from kip.
@joh4n : i reproduced your CreateContainerConfigError
error in my local setup. The cause of failure is below:
Warning Failed 17s (x5 over 70s) kubelet, m01 Error: secret "provider-secret" not found
This is because of minikube kustomize overlay scripts being out of sync with base. Let me fix that and share an update by the end of day PT wednesday.
from kip.
@joh4n : the issue is now fixed in master. There were two issues:
-
Instructions in the beginning of
overlays/minikube/kustomization.yaml
were outdated. This is what you followed and ran into failed apply. -
We switched from listing AWS credentials in
provider.yaml
to specifying it via a secret in some of the deploy paths (minikube, provision your own cluster, burst kip workloads from on-prem cluster to AWS/GCP, etc). Some of the scripts inoverlays/minikube
assumed old format and some assumed new format. Apologies for this issue. i fixedoverlays/minikube
to use AWS credentials inprovider.yaml
by default and not rely on a secret.
Master now has fixes for both 1 and 2. https://github.com/elotl/kip/tree/master/deploy/manifests/kip/overlays/minikube/README.md
has the latest instructions. i tested the latest instructions with latest bits. Please let me know how the latest bits work for you. Thank you for your patience!
from kip.
@joh4n : checking in to see if you were able to make progress with your minikube env? Please let us know if there are any further issues. Thanks!
from kip.
Related Issues (20)
- Add map of instance families that support running as dedicated hosts to instance selector
- Provisioning documentation and configuration for standing up a cluster that can run mac1 instances
- Implement instance selector back-pressure
- Make sure dedicated host is "available" before launching an instance onto it
- Make sure the Base AMI is ready for the VM template HOT 1
- Set all needed EBS params in RunInstance request
- Redundant Ticker HOT 1
- Implement GetDNSInfo for azure
- Document provider configuration for azure
- Fix parsing virtualNetwork name for azure
- Create azure VM cell image HOT 1
- KIP init-cert does not work on EKS 1.19
- updating pricing data for EC2 instances stopped working
- KIP does not support BoundServiceAccount Token Volume
- Terraform main.tf doesn't work with mac with apple m1 chip
- Add smoke test for GKE
- service account token missing in pod HOT 1
- failing container does not increase Restart count, and log content is unexpected
- issues deploying pods to kip provider in minikube
- Singularity support in KIP provider
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.
from kip.