No. Kubernetes is not aware of perf differences between CPU or RAM hardware.
Can you describe why you are looking for such a solution? What's your
specific use case?
On Sep 20, 2017 4:04 PM, "z3ro" wrote:
> is kubernetes aware of the performance difference between say a nehalem
> and a broadwel
is kubernetes aware of the performance difference between say a nehalem and
a broadwell core?
and ram performance?
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails
Hello,
I know I have seen some discussion on this topic both in this group and on the
Kubernetes github issues, but I haven't found a good solution, so I thought I
would add my experience to the mix.
Earlier this week, Oraclelinux added Kubernetes support through its yum
repositories. I
On Wed, Sep 20, 2017 at 5:25 AM, Shashank Dutt Jha
wrote:
>
> $ kubectl apply -f kuber-agent.yml
> The Deployment "agent-kuber" is invalid:
> * spec.template.spec.volumes[0].hostPath: Forbidden: may not specify more
> than 1 volume type
You have more than one source listed in a volume block
> *
And if you are on different machines, you need to push that image
somewhere so it can be pulled by kubelet
On Wed, Sep 20, 2017 at 9:49 AM, Warren Strange
wrote:
>
>
> ImagePullBackOff means that Kubernetes can not find the image.
>
> You have:
> image: agentc
>
> You need:
>
> image: library/a
ImagePullBackOff means that Kubernetes can not find the image.
You have:
image: agentc
You need:
image: library/agentc:latest
This also assumes you have done a "docker build" direct to the docker
daemon that your Kubernetes cluster is using.
If you are using minikube, you must make sure
There's no supported way to do that, in part because it would give up
all of the Service names that kubernetes provides. I don't know what
would happen if you tried to volumeMount a file over /etc/resolv.conf
- might be worth a shot.
On Wed, Sep 20, 2017 at 3:15 AM, Simone D'Andreta
wrote:
> Hel
It seems like it.
The documentation seems pretty straightforward:
https://kubernetes.io/docs/tasks/debug-application-cluster/audit/
Thank you!
Best,
George
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe
Thank you for your post.
I too am trying different methods/stacks as well to pxe boot a 42u bare metal
rack into a cluster. os running in ram of course. what was your experience
with Rancher and core os together? Do you recommend Bootkube+matchbox over
coreosmatchbox/ rancher? I like ranche
Hello everyone!
I'm trying to whitelist an IP to access a deployment inside my Kubernetes
cluster. (Restrict all traffic but the whitlisted IP's)
I looked for some documentation online about this, but I only found the
ingress.kubernetes.io/whitelist-source-range
for ingress to grant access to
$ kubectl apply -f kuber-agent.yml
The Deployment "agent-kuber" is invalid:
* spec.template.spec.volumes[0].hostPath: Forbidden: may not specify more
than 1 volume type
* spec.template.spec.volumes[0].persistentVolumeClaim: Forbidden: may not
specify more than 1 volume type
* spec.template.spec.con
Hello,
I wanted to know if there is a way to override DNS settings for pods (not
per cluster). I tried to use HostAliases but it only creates an A record
for that entry. I basically need a NS record cause I need to point to
different Consul clusters and then Consul must be able to do service
di
I get this error now:
$ kubectl apply -f kuber-agent.yml
error: error validating "kuber-agent.yml": error validating data: found
invalid field path for v1.Volume; if you choose to ignore these errors,
turn validation off with --validate=false
apiVersion: apps/v1beta1
kind: Deployment
metadata:
Now I get following error: following your suggestion
$ kubectl apply -f kuber-agent.yml
error: error validating "kuber-agent.yml": error validating data: found
invalid field volumes for v1beta1.DeploymentSpec; if you choose to ignore
these errors, turn validation off with --validate=false
kuber-
I have created an image using Docker command
docker build -t library/app-agentk .
Then I have config file
piVersion: apps/v1beta1
kind: Deployment
metadata:
name: agent-deployment
spec:
replicas: 1 # tells deployment to run 2 pods matching the template
template: # create pods using pod d
15 matches
Mail list logo
