Thanks, it's also useful.
What I was more looking for was a proper ingress to access the dashboard
from external..
On Thursday, December 7, 2017 at 4:33:42 PM UTC-8, ale...@gmail.com wrote:
>
> Please check
>
Please check
https://github.com/kubernetes/ingress-nginx/blob/master/docs/examples/customization/custom-vts-metrics-prometheus/README.md
On Thursday, December 7, 2017 at 1:15:52 PM UTC-3, Jerry Hwang wrote:
> Thanks. I am interested in accessing nginx controller dashboard.
> Do you have an
*How to pass arguments to Kubernetes POD were succesfull, however Google
states, that templates are needed for configurability.*
https://stackoverflow.com/questions/47700482/kubernetes-pod-arguments-are-not-displayed-in-service-under-args-without-error/47703631#47703631
On Thursday,
Tim,
I could make a configurable REST API for database, that accepts Ipaddress,
and Port, via REST with Json message. This could work at run time
dynamically, so that I can configure the backend database with its
necessary settings, and since I can setup a Singleton class, this could be
Tim,
Check out the REST Spring Boot project:
https://github.com/quantum-fusion/springboot_swagger_example-master-cassandra
The goal of this project, is to offer a configurable software architecture,
for a distributed Application, that runs across a global grid of
distributed databases. Since
Tim,
Is there any other way to have my Spring-Boot controller accept arguments
from the java or Docker command line? I need this feature, because I need
to make the decision, of which ip address, and port number, are needed for
my database backend at run time. (i.e. when I decide how many
The Kubernetes Pod should properly accept arguments as does Docker.
See Pod.yaml
https://github.com/quantum-fusion/springboot_swagger_example-master-cassandra/blob/master/Kubernetes/singlePod.yaml
The problem is that the program accepts arguments from java command line:
java -jar
With Daemonset now everything is working properly.
Anyway I'm using Kubernetes 1.8.1-gke.1
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
You want a template expander before you get to kubectl. Otherwise, the
thing that is running isn't reflected by any versionable artifact.
Because templating is a high-opinion space, we do not (currently) have one
that is built-in.
On Dec 7, 2017 10:12 AM, "Henry Hottelet"
Thanks. I am interested in accessing nginx controller dashboard.
Do you have an ingress example to assist to access it?
On Wednesday, December 6, 2017 at 7:55:18 PM UTC-8, ale...@gmail.com wrote:
>
> Hi Jerry,
>
> You are being directed to the default backend (expected behavior without a
> host
Is there not a way to pass arguments from command line to the Pod
specification? There should be, because this is not the first time that a
Docker argument is needed when calling a Pod instance, whether dynamic or
staticly defined.
I could have Pod1.yaml, Pod2.yaml, and have an Ipaddress,
Kubectl is not a templating system, which is what you are asking for.
Create/Apply are declarative plumbing, suitable to things you would check
in to source control. There are porcelain commands, eg. kubectl run, which
are closer to docker run, but less suitable to source control.
On Dec 7, 2017
A problem:
Docker arguments will pass from command line:
docker run -it -p 8080:8080 joethecoder2/spring-boot-web
-Dcassandra_ip=127.0.0.1 -Dcassandra_port=9042
However, when I do:
kubectl create -f ./singlePod.yaml
Kubernetes POD arguments will not pass from singlePod.yaml file:
Oh, I thought you wanted on different hosts but not as many pods as hosts.
If you want that's daemonset guarantees that (even if more nodes are
created later, etc.)
And what Kubernetes version are you using? There is some kind of support to
upgrade them in recent versions IIRC (not used that more
I assume this is a GKE cluster?
When scaling up, GKE will automatically resize your master if the cluster
is too big for the current master size. This will cause the master to
restart causing a brief unavailability of Kubernetes API.
This is not a new feature, but it will become visible after
Today during a deploy I get a pod with 2 containers -,-
I can confirm that the best solution to make sure you have only one pod per
node is using the DaemonSet.
Unfortunately using the approach to reapply the deployment yaml does not
guarantee that after deployment each node has only a single
I have a cluster running on GCE and I want to use traefik as a loadbalancer for
my services.
Using master version 1.7.8-gke.0 and Node version: 1.7.6 and my role is Owner
of the project.
When i'm trying to give permissions to the traefik ingress controller I receive
this error:
Error from
17 matches
Mail list logo