User Guide
What is Kubernetes?
User Guide
Accessing the Cluster
Web UI (Dashboard)
Workload Deployment and Management
Batch Jobs
Service Discovery and Load Balancing
Containers and Pods
Monitoring, Logging, and Debugging Containers
Creating a Cluster
Picking the Right Solution
Running Kubernetes on Your Local Machine
Running Kubernetes on Turn-key Cloud Solutions
Running Kubernetes on Google Container Engine
Running Kubernetes on Google Compute Engine
Running Kubernetes on AWS EC2
Running Kubernetes on Azure Container Service
Running Kubernetes on Azure
Running Kubernetes on CenturyLink Cloud
Running Kubernetes on IBM SoftLayer
Running Kubernetes on Multiple Clouds with Stackpoint.io
Running Kubernetes on Custom Solutions
Creating a Custom Cluster from Scratch
Installing Kubernetes on Linux with kubeadm
Custom Cloud Solutions
On-Premise VMs
Bare Metal
Offline
Fedora via Ansible
Fedora (Single Node)
Fedora (Multi Node)
CentOS
CoreOS on AWS or GCE
Kubernetes on Ubuntu
Ubuntu
Kubernetes on Ubuntu
Validation
Backups
Upgrades
Scaling
Setting up Kubernetes with Juju
Monitoring
Networking
Security Considerations
Storage
Troubleshooting
Decommissioning
Deploying Kubernetes with Calico Networking on Ubuntu
Operational Considerations
Glossary and Terminology
Local Kubernetes development with LXD
Logging
Manually Deploying Kubernetes on Ubuntu Nodes
Windows Server Containers
Validate Node Setup
Portable Multi-Node Cluster
Building Large Clusters
Running in Multiple Zones
Building High-Availability Clusters
Downloading or Building Kubernetes
Administering Clusters
Admin Guide
Cluster Management Guide
Cluster Management Guide
kubeadm reference
Installing Addons
Audit in Kubernetes
Setting up High-Availability Kubernetes Masters
Sharing a Cluster with Namespaces
Namespaces Walkthrough
Setting Pod CPU and Memory Limits
Pod Disruption Budget
Resource Quotas
Applying Resource Quotas and Limits
Limiting Storage Consumption
Guaranteed Scheduling For Critical Add-On Pods
Using Sysctls in a Kubernetes Cluster
Kubernetes Components
Configuring Kubernetes Use of etcd
Using Multiple Clusters
Changing Cluster Size
Configuring Multiple Schedulers
Networking in Kubernetes
Using DNS Pods and Services
Setting Up and Configuring DNS
Master-Node communication
Network Plugins
Static Pods
Configuring kubelet Garbage Collection
Configuring Out Of Resource Handling
Configuring Kubernetes with Salt
Monitoring Node Health
AppArmor
Administering Federation
Logging
Agent Logging
The juju debug-log will show all of the consolidated logs of all the Juju agents running on each node of the cluster. This can be useful for finding out why a specific node hasn’t deployed or is in an error state. These agent logs are located in /var/lib/juju/agents on every node.
See the Juju documentation for more information.
Managing log verbosity
Log verbosity in Juju is set at the model level. You can adjust it at any time:
juju add-model k8s-development --config logging-config='<root>=DEBUG;unit=DEBUG'
and later
juju config-model k8s-production --config logging-config='<root>=ERROR;unit=ERROR'
In addition, the jujud daemon is started in debug mode by default on all controllers. To remove that behavior edit /var/lib/juju/init/jujud-machine-0/exec-start.sh on the controller node and comment the --debug section.
It then contains:
#!/usr/bin/env bash
# Set up logging.
touch '/var/log/juju/machine-0.log'
chown syslog:syslog '/var/log/juju/machine-0.log'
chmod 0600 '/var/log/juju/machine-0.log'
exec >> '/var/log/juju/machine-0.log'
exec 2>&1
# Run the script.
'/var/lib/juju/tools/machine-0/jujud' machine --data-dir '/var/lib/juju' --machine-id 0 # --debug
Then restart the service with:
sudo systemctl restart jujud-machine-0.service
See the official documentation for more information about logging and other model settings in Juju.