Creating Google Kubernetes Engine Deployments Reviews

Jasiel M. · Reviewed 3 ay ago

Manuel C. · Reviewed 3 ay ago

Bryan C. · Reviewed 3 ay ago

Julieta G. · Reviewed 3 ay ago

Very Satisfed

Paul Amaury S. · Reviewed 3 ay ago

Samir A. · Reviewed 3 ay ago

adony g. · Reviewed 3 ay ago

Jordy P. · Reviewed 3 ay ago

Edgar R. · Reviewed 3 ay ago

Miguel H. · Reviewed 3 ay ago

Edgar A. · Reviewed 3 ay ago

easy to follow & understand

Arief S. · Reviewed 3 ay ago

Rodrigo T. · Reviewed 3 ay ago

Bhanu A. · Reviewed 3 ay ago

Mayuresh K. · Reviewed 3 ay ago

Raul Emmanuel B. · Reviewed 3 ay ago

Mahendra H. · Reviewed 3 ay ago

Stan D. · Reviewed 3 ay ago

Nahum S. · Reviewed 3 ay ago

Johan S. · Reviewed 3 ay ago

Diana Carolina N. · Reviewed 3 ay ago

The service configuration used in the lab does not ensure that all requests from a single client will always connect to the same Pod. Each request is treated separately and can connect to either the normal nginx deployment or to the nginx-canary deployment. This potential to switch between different versions may cause problems if there are significant changes in functionality in the canary release. To prevent this you can set the sessionAffinity field to ClientIP in the specification of the service if you need a client's first request to determine which Pod will be used for all subsequent connections.

Ayan S. · Reviewed 3 ay ago

Shuo Z. · Reviewed 3 ay ago

fr m. · Reviewed 3 ay ago

Danail V. · Reviewed 3 ay ago