The built in go http.Fileserver handles If-Modified-Since in the
header by comparing it with the last modified date on the
file/directory. Since the file is unaltered when we switch to a
new container, that results in 304s when trying to fetch data.json, so
the browser doesn't fetch the new picture after doing a rolling update.
Separate issue, the Dockerfile ADD command was being interpreted as
`copy html/data.json into a directory called 'html/kitten.jpg '`,
instead of the `copy these 2 files into root`. Changed to separate
commands using COPY, per recommended dockerfile practices.
This commit addresses issue #1571, which requests that all internal
Kubernetes links are swapped to relative ones to better facilitate
browsing of documentation on local forks, not to mention make the
documentation have less needless boilerplate.
As a replacement of a single SERVICE_HOST variable, offer a FOO_SERVICE_HOST
variable. This will help ease the transition to ip-per-service, where there
is no longer a single service host.
# *** ERROR: *** Some files are missing the required boilerplate
# header from hooks/boilerplate.txt:
# examples/guestbook/redis-slave/run.sh
#
# Your commit will be aborted unless you fix these.
# COMMIT_BLOCKED_ON_BOILERPLATE
Port of current guestbook's README.md
Fix guestbook pod and service names
Add go boilerplate
Use role label for redis pods
Give service.containerPort a name based value
This gives better env variable keys like REDIS_MASTER_SERVICE_REDIS_SERVER_ADDR, etc.
Avoid unnecessarily long names for service (esp in env vars)
Adding guestbook deploy/destroy scripts for k8s
These are probably only useful for quick testing. Maybe remove them
before merging the pull request.
Part of avoiding long names for services
Update Dockerfiles to git clone from Google's repo
Use correct service names while deleting them
Fix the script usage path.
K8s is not go gettable. Use git clone instead.
Using my fork in the Dockerfile to release and update to the docker hub
image.
Doesn't delete all pods if you remove controller too soon
Run the command in a shell to substitute env vars. Workaround for GoogleCloudPlatform/kubernetes#1309
GoogleCloudPlatform in lieu of my fork in Dckrfile
Some directory structure changes for guestbook src
README that explains the build process for source
Strip down the html and css to absolute essentials
Reformat JS according to Google's guidelines
Also added code to set random colors for elements.
Handle repetitive error checks using a common func
Also uses @roberthbailey’s stripped down code for reading env vars
infoString isn't really a string. Use info instead
Remove deploy.sh/destroy.sh scripts
Bind submit instead of keypress to capture submit
Add links to /env and /info in the footer
Reformat the JS
Incorporating suggestions by @filbranden
License boilerplate and some fixes to release.sh
Update README.md
Update README.md
Add building on boot2docker info to README
Accept docker bin path as a param for building
Use kubernetes user to host the image on registry
Don't get included in k8s's recursive build deps
https://github.com/GoogleCloudPlatform/kubernetes/pull/1299#discussion_r
17638061
* Make Codec separate from Scheme
* Move EncodeOrDie off Scheme to take a Codec
* Make Copy work without a Codec
* Create a "latest" package that imports all versions and
sets global defaults for "most recent encoding"
* v1beta1 is the current "latest", v1beta2 exists
* Kill DefaultCodec, replace it with "latest.Codec"
* This updates the client and etcd to store the latest known version
* EmbeddedObject is per schema and per package now
* Move runtime.DefaultScheme to api.Scheme
* Split out WatchEvent since it's not an API object today, treat it
like a special object in api
* Kill DefaultResourceVersioner, instead place it on "latest" (as the
package that understands all packages)
* Move objDiff to runtime.ObjectDiff
v2: Resolve issues from comments, fix bugs in update-demo example, rename files for clarity, add turn-down steps.
v3: Add more set commands, clean up rest of env var checks.
Use images and some better formatting. Also add scripts to help prevent typos.
This based on an improved version done by Julia Ferraioli. She came up with the cool images.
This is some cleanup that has been needed for a while.
There's still one more step that could usefully be done, which is to
split up our api package into the part that provides the helper
functions and the part that provides the internal types. That can come
later.
The v1beta1 package is now a good example of what an api plugin should
do to version its types.